[
https://issues.apache.org/jira/browse/STANBOL-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314442#comment-14314442
]
Edi Bice commented on STANBOL-1411:
-----------------------------------
That it was! It's working now and I'm able to simulate it. I'm thinking of
adding the check for origin in the section below (from public static
SavedEntity createFromTextAnnotation(TripleCollection graph, UriRef
textAnnotation) in SavedEntity.java):
{code}
while (suggestions.hasNext()) {
UriRef entityAnnotation = (UriRef) suggestions.next().getSubject();
Suggestion suggestion =
Suggestion.createFromEntityAnnotation(graph, entityAnnotation);
if (suggestion != null) {
suggestionList.add(suggestion);
if (suggestion.getSite() != null) {
entityhubSites.add(suggestion.getSite());
} // else check for origin {
//}
}
}
{code}
Was struggling during simulation as I was using
EnhancementEngineHelper.getString(graph, textAnnotation,
Properties.ENHANCER_ORIGIN) which was returning null. Tried with
entityAnnotation as well. Eventually I realized I should be using
EnhancementEngineHelper.getReference(graph, entityAnnotation,
Properties.ENHANCER_ORIGIN) since I've configured origin to a URI
(http://dbpedia.org).
Then I noticed in https://issues.apache.org/jira/browse/STANBOL-1391 your
comment about all the possible values (and types) of that property:
"A single value can be configured as String. If the value is an absolute URI an
UriRef value will be parsed. In other cases the value will be a Literal."
Should I try getString, getReference, ... until one succeeds or is there a
better way?
> Make the MLT disambiguation engine work with the FST linking engine
> -------------------------------------------------------------------
>
> Key: STANBOL-1411
> URL: https://issues.apache.org/jira/browse/STANBOL-1411
> Project: Stanbol
> Issue Type: New Feature
> Components: Enhancer
> Affects Versions: 0.12.0, 1.0.0
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Fix For: 1.0.0, 0.12.1
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The Solr MLT disambiguation engine uses the {{entityhub:site}} property to
> check if a suggested Entity originates from the Entityhub Site that is
> disambiguated.
> This {{entityhub:site}} is written by the EntityhubLinkingEngine, but not by
> the FST linking engine as this engine directly uses a SolrCore and does -
> strictly speaking - not know from (depend on) any Entityhub site.
> However STANBOL-1391 added the feature to the FST linking engine to provide
> origin information for annotations. Those do use the {{fise:origin}} property.
> This issue is about extending the MLT disambiguation engine to consider
> {{fise:origin}} as a fallback to {{entityhub:site}}. This will allow users
> that want to use MLT disambiguation together with FST linking by configuring
> the name of the Entityhub site as value of the
> {{enhancer.engines.linking.lucenefst.origin}} property for the FST linking
> engine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
