Rupert Westenthaler created STANBOL-792:
-------------------------------------------

             Summary: Extend the NamedEntityExtraction engine to support custom 
NameFinder Models
                 Key: STANBOL-792
                 URL: https://issues.apache.org/jira/browse/STANBOL-792
             Project: Stanbol
          Issue Type: Sub-task
            Reporter: Rupert Westenthaler
            Assignee: Rupert Westenthaler


The NER engine needs the mappings for an {ner-model} to its {language}
and the extracted {entity-type}. Currently this works by a constant
defining the mappings for persons, organizations and places. NLP
models are loaded by using the OpenNLP service (defined by the
o.a.stanbol.commons.opennlp module).

To configure additional models and types I would suggest to add an
additional configuration property that uses the following syntax

    {model-file-name};lang={language};type={entity-type}

The OpenNLP TokenNameFinderModel would be loaded from the configured
"{model-file-name}" via the Stanbol DataFileProvider service.
practically this means that users would need to copy their custom
models to the "{stanbol.home}/datafiles" directory.

The language parameter "lang={language}" would specify the language
supported by this model. The "type={entity-type}" parameter would
specify the dc-type value set for fise:TextAnnotations created for
named entities extracted by the model.

This new feature should also allow to override the currently used defaults by 
specifying e.g.

    myCustomPersonModel_en.zip;lang=en;type=dbp-ont:Person

This would override the default configuration for loading the Person NameFinder 
model for English.


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