[
https://issues.apache.org/jira/browse/STANBOL-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691893#comment-13691893
]
Rupert Westenthaler commented on STANBOL-1111:
----------------------------------------------
This feature will bring full paging (offset, limit) support to the
EntitySearcher. This is necessary because in cases where a lot of suggestion
are filtered the EntityLinking process needs to be able to request additional
results.
The following factors are used to decide how many Entities are processed:
(0) lookupLimit := max(10, MAX_SUGGESTION*2*searchTokens.size())
... means always 10 with the default config (max suggestions: 3, max
searchtokens: 2)
Search until
(1) no more results are available
(2) we have more as MAX_SUGGESTION suggestions
(3) the number of processed Entities is smaller as two times the suggestions
... this are the number of Entities not filtered based on this configuration
(4) the number of requested Entities is smaller as two times the lookup limit.
... this ensures that never more as two queries are made (for performance
reasons)
> Support Entity type based restrictions for EntityLinking
> --------------------------------------------------------
>
> Key: STANBOL-1111
> URL: https://issues.apache.org/jira/browse/STANBOL-1111
> Project: Stanbol
> Issue Type: Sub-task
> Components: Enhancement Engines
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> This will allow to configure a list of Entity types that are considered
> (white listed) and/or ignored (black listed) during linking.
> This will be a new configuration option for the EntityLinkerConfig and use a
> similar syntax as the Language configuration.
> {type} ... white listed
> !{type} ... black listed
> * ... allow any (default as long there is no white listed type)
> If an Entity has both an white listed and an black listed type the ordering
> of the configuration will considered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
