[
https://issues.apache.org/jira/browse/STANBOL-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489387#comment-13489387
]
Rupert Westenthaler commented on STANBOL-792:
---------------------------------------------
While working on that I decided that it is a better solution to keep the
current "NamedEntityExtractionEnhancementEngine" as is and implement the
feature for extracting NamedEntities with custom OpenNLP NameFinder models as
an own Enhancement Engine.
Both engines will use the existing
org.apache.stanbol.enhancer.engines.opennlp.impl.NEREngineCore
to do the actual work, but only implement the
* parsing the user provided configuration
* configuration of the NEREngineCore
The main advantage of this approach is the the configuration of the existing
NER engine will stay as easy as now (most users will be OK with the default
configuration).
I will update the description of the Issue with the name/configuration of the
new EnhancementEngine as implementation progress.
> 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
