You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2013/04/24 13:17:16 UTC

[jira] [Resolved] (STANBOL-1051) EntityLinking does not correctly handle Phrase, NER and Pos annotations with unknown probability

     [ https://issues.apache.org/jira/browse/STANBOL-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rupert Westenthaler resolved STANBOL-1051.
------------------------------------------

    Resolution: Fixed

fixed with http://svn.apache.org/r1471366 for the EntityLinking engine.
http://svn.apache.org/r1471367 fixes the same issue for the Sentiment engines
                
> EntityLinking does not correctly handle Phrase, NER and Pos annotations with unknown probability
> ------------------------------------------------------------------------------------------------
>
>                 Key: STANBOL-1051
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1051
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Enhancement Engines
>    Affects Versions: enhancement-engines-0.10.0
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>
> Annotations with unknown probability are ignored by the EntityLinkingEngine as the UNKNOWN_CONFIDENCE value (-1) is not correctly handled and therefore confidence values are interpreted as lower than the processing threshold.
> This means that all Phrase, NER and POS annotations with unknown probability are getting ignored. 
> Most users will not be affected by that as all currently integrated NLP frameworks do provide probabilities. However users that have integrated custom NLP engines might get affected by this.
>  For EntityLinking annotations with unknown probability should be always accepted. However note because the processing of Annotations is ordered any Annotation with a known probability will be considered first.

--
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