[STANBOL-740] Adopt the KeywordLinkingEngine to use the AnalyzedText content part

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: enhancement-engines-0.10.0
• Component/s: Enhancement Engines
• Assignee: Rupert Westenthaler
• Reporter: Rupert Westenthaler
• Created: 10/Sep/12 10:13
• Updated: 02/May/13 02:30
• Resolved: 21/Nov/12 14:39

Description

The KeywordLinkingEngine currently does both NLP processing AND linking against the target vocabulary. Up to now this was the only possibility as separating those two things was not feasible with the limitations of the RDF metadata.

With the introduction of the AnalyzedText content part the NLP processing part needs no longer be part of the KeywordLinkingEngine.

This issue covers

• removal of the NLP related functionality from the KeywordLinkingEngine
• reimplementation of the linking part on top of the API provided by the AnalyzedText contentpart
• add support fore new features of the NLP chain
• use lemmas - if available - for entity lookup
• use POS tagset mappings to the OLIA ontology to decide what tokens to lookup

After this change the KeywordLinkingEngine will also be able to work in combination with any NLP framework that is integrated with the Stanbol NLP components (writes its data to the AnalyzedText content part).

Issue Links

• is superceded by: STANBOL-812 Rename the AnalyzedText based KeywordLinkingEngine to EntityhubLinkingEngine
• relates to: STANBOL-823 Refactor EntityLinkingEngine so that it does no longer depend on the Stanbol Entityhub Component