[ 
https://issues.apache.org/jira/browse/STANBOL-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473186#comment-13473186
 ] 

Rupert Westenthaler edited comment on STANBOL-706 at 10/10/12 12:47 PM:
------------------------------------------------------------------------

marking this as resolved with http://svn.apache.org/viewvc?rev=1396570&view=rev.

Further improvements to this Engine should be carried out in own issues.
                
      was (Author: rwesten):
    fixed with http://svn.apache.org/viewvc?rev=1396568&view=rev
                  
> DBpedia Spotlight EnhancementEngines integration
> ------------------------------------------------
>
>                 Key: STANBOL-706
>                 URL: https://issues.apache.org/jira/browse/STANBOL-706
>             Project: Stanbol
>          Issue Type: New Feature
>          Components: Enhancer
>    Affects Versions: 0.9.0-incubating
>            Reporter: Iavor Jelev
>            Assignee: Rupert Westenthaler
>         Attachments: dbpediaspotlightintegration.rar
>
>
> In the process of the early adopters programme of the IKS we developed 4 
> EnhancementEngines, which integrate the different aspects of DBpedia 
> Spotlight in Apache Stanbol. We would like to contribute them, so they can 
> eventually become a part of the Stanbol Stack. The engines are as follows:
> - dbpediaspotlightannotate - spots the potential mentions, retrieves the 
> candidate DBpedia resources, disambiguates them if needed, and links the 
> mentions to the best one
> - dbpediaspotlightcandidates - same as annotate, but does not disambiguate 
> the candidates for each mention. Rather it returns the top K ones.
> - dbpediaspotlightdisambiguate - does not do spotting, it just selects the 
> candidates for the given mentions and does disambiguation.
> - dbpediaspotlightspot - does only spotting, no candidate resource selection, 
> disambiguation or linking

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

Reply via email to