View Component 26.3
View Component Help

# EntityMatchLimitN

The maximum number of matches to return for the entities specified by the corresponding EntityN parameter. When Named Entity Recognition reaches the limit it stops searching for those entities, so no further matches are returned and Named Entity Recognition does not spend time looking for them.

If the `EntityN` parameter specifies multiple entities, using a wildcard or a comma-separated list, the limit applies separately to each entity. For example, the following configuration would permit up to three matches for British names, and up to three for French names, and so on:

    Entity0=pii/name/*
    EntityMatchLimit0=3

The limit is applied after post-processing, so any matches that are discarded by post-processing do not count towards the limit.

You might set this parameter if you want to see some matches for a given entity but would prefer to ignore further matches in favor of reducing the processing time.

NOTE: In the Named Entity Recognition SDKs, you can turn off an entity by setting `EdkSessionSetEntityMatchLimit` (or an equivalent) to zero. However, you cannot configure a match limit of zero in the configuration file.

Type: | Integer
Default: | unlimited
Range: | Minimum: 1 NOTE: If you use a non-valid value, View Component uses the default setting (unlimited matches)
Required: | No
Configuration Section: | MyRedactionSettings
Example: | With the following configuration Named Entity Recognition returns a maximum of three matches for the `pii/name/gb` entity. `Entity0=pii/name/gb EntityMatchLimit0=3`
See Also: | EntityN

Copyright 2026 Open Text
Version 26.3 | Last updated July 2026

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery View Component 26.3

Topic Title: EntityMatchLimitN