For each pre-filter task that you want to configure, you set a regular expression that specifies how to find potential matches, and you set the amount of text Eduction must use on either side of the potential match in the more detailed match.
NOTE: Eduction runs all your configured prefiltering tasks for all input text, so ensure that your prefilter task applies to all your configured grammars and entities. Use a different configuration for any entities that you do not want to prefilter.
To configure a prefilter task
[Eduction]
section, add a PreFilterTaskN
parameter, where N
is a number starting from 0 for the first task. Set this parameter to the name of a configuration section where you define your pre-filter task.Regex
to a regular expression value that finds potential matches in your text.WindowCharsBeforeMatch
and WindowCharsBeforeMatch
to the number of characters before and after the potential match segment to use as the match window.For example:
[Eduction] PrefilterTask0=AddressPrefilter [AddressPrefilter] Regex=\d{1,7} WindowCharsBeforeMatch=100 WindowCharsAfterMatch=100
For more details about these parameters, see Eduction Parameter Reference.
TIP: To use pre-filtering tasks through the C and Java Eduction APIs, you must create your Eduction engine from a configuration file. See Standalone API Usage (C) or Standalone API Usage (Java).
|