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 2012/10/31 15:51:11 UTC

[jira] [Created] (STANBOL-793) Extend the NamedEntityLinking Engine to support abritary configureable NamedEntity types.

Rupert Westenthaler created STANBOL-793:
-------------------------------------------

             Summary: Extend the NamedEntityLinking Engine to support abritary configureable NamedEntity types.
                 Key: STANBOL-793
                 URL: https://issues.apache.org/jira/browse/STANBOL-793
             Project: Stanbol
          Issue Type: Sub-task
            Reporter: Rupert Westenthaler


The current implementation provides configuration parameters for dbp-ont:Person, dbp-ont:Organisation and dbp-ont:Place. While it is possible to activate/deactivate those typed it is not possible to link NamedEntities of other types.

To allow that it is necessary to implement a different approach to configure the mappings for linked
fise:TextAnnotations dc:type values.

The suggestion is to use a configuration similar to the "type mapping"
[1] as already used by the KeywordLinkingEngine. The Syntax would be
like

     {dc-type} > {vocabulary-type}; {vocabulary-type}; ...
     {dc-type} > *
     {dc-type}

where the {dc-type} would be the value of the dc-type property of the
TextAnnotation and {vocabulary-type} is the rdf:type value required
for linked Entities in the vocabulary linked against. * represents the
wild-card (any type) and {dc-type} is a shorthand for {dc-type} >
{dc-type}

The current default mappings would be represented in this syntax by

    dbp-ont:Place
    dbp-ont:Person
    dbp-ont:Organisation

I would suggest to keep support for the current properties for not
braking backward compatibility.

[1] http://stanbol.apache.org/docs/trunk/components/enhancer/engines/keywordlinkingengine.html#type-mappings-syntax

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