Author: buildbot
Date: Tue Nov 19 14:21:48 2013
New Revision: 887228
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/entityhublinking.html
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/entitylinking.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 19 14:21:48 2013
@@ -1 +1 @@
-1533041
+1543437
Modified:
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/entityhublinking.html
==============================================================================
---
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/entityhublinking.html
(original)
+++
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/entityhublinking.html
Tue Nov 19 14:21:48 2013
@@ -90,7 +90,7 @@
</div>
<h1 class="title">The Entityhub Linking Engine: Linking NLP processed Text
with Vocabularies managed by the Stanbol Entityhub</h1>
<p>The EntityhubLinkingEngine is the successor of the <a
href="keywordlinkingengine">KeywordLinkingEngine</a>. It is based on the <a
href="entitylinking">EntityLinkingEngine</a> configured with an <a
href="entitylinking#entitysearcher">EntitySearcher</a> that can link Entities
managed by either the Entityhub, ReferencedSites as well as ManagedSites. The
EntityhubLinkingEngine does not implement the <a
href="index">EnhancementEngine</a> interface itself. It only configures an
instance of the <a href="entitylinking">EntityLinkingEngine</a>.</p>
-<p>For a detailed documentation of the linking process please see the
documentation of the <a href="entitylinkingengine">EntityLinkingEngine</a>.
This document only focuses on the configuration and the usage of this
Engine.</p>
+<p>For a detailed documentation of the linking process please see the
documentation of the <a href="entitylinking">EntityLinkingEngine</a>. This
document only focuses on the configuration and the usage of this Engine.</p>
<h2 id="configuration">Configuration</h2>
<p>The configuration of the EntityhubLinkingEngine supports the following
options. First it allows to configure the two properties common to all
enhancement engines</p>
<ul>
@@ -101,7 +101,7 @@
<ul>
<li><strong>Referenced Site</strong>
<em>(enhancer.engines.linking.entityhub.siteId)</em>: The name of the
ReferencedSite of the Stanbol Entityhub that holds the controlled vocabulary to
be used for extracting Entities. "entityhub" or "local" can be used to extract
Entities managed directly by the Entityhub.</li>
</ul>
-<p>Finally it supports all configuration options supported by the <a
href="entitylinkingengine">EntityLinkingEngine</a>.</p>
+<p>Finally it supports all configuration options supported by the <a
href="entitylinking">EntityLinkingEngine</a>.</p>
<ul>
<li><a href="entitylinking#text-processing-configuration">Text Processing
Configuration</a>: This defines what languages are enabled and is also used to
configure how NLP processing results are used by the Engine</li>
<li><a href="entitylinking#entity-linker-configuration">Entity Linking
Configuration</a>: This defines how entity are searched in the vocabulary and
search results are matched with the text. It also allows to configure
'dc:type's for created 'fise:TextAnnotation's and if entity information are
included in the enhancement results or not.</li>
Modified:
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/entitylinking.html
==============================================================================
---
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/entitylinking.html
(original)
+++
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/entitylinking.html
Tue Nov 19 14:21:48 2013
@@ -260,6 +260,7 @@ Configuration wise this will pre-set the
</ul>
<p>The parameters below are used to configure the matching process.</p>
<ul>
+<li><strong>Minimum Chunk Match Score</strong>
<em>(enhancer.engines.linking.minChunkMatchScore)</em>: If the mention of an
Entity is within a Chunk (e.g. a Noun Phrase) this specifies the minimum
percentage of Tokens the detected Entity must match to be accepted. Only
matchable tokens of phrases are counted (e.g. for the <code>lovely Julia
Roberts</code> only <code>Julia Roberts</code> would count as lovely is an
adjective). By default this is set to <code>0.51</code> so an Entity with a
label <code>Julia</code> would not be accepted. <em>NOTE:</em> This only
considers 'processable' chunks. Because of that it depends also on the
<em>pc</em> parameter of the Language Processing configuration; This feature
was introduced with <a
href="https://issues.apache.org/jira/browse/STANBOL-1211";>STANBOL-1211</a>.</li>
<li><strong>Minimum Token Match Score</strong>
<em>(enhancer.engines.linking.minTokenScore)</em>: This defines how well single
tokens of the text need to match single tokens in the label so that they are
considered as matching. This parameter configures the lower limit. However the
actual token match score does also influence the overall matching scores for
labels with the text. So non exact matches will decrease matching scores for
the whole label with the text.</li>
<li><strong>Min Label Score</strong>
<em>(enhancer.engines.linking.minLabelScore)</em> [0..1]::double: The "Label
Score" [0..1] represents how much of the Label of an Entity matches with the
Text. It compares the number of Tokens of the Label with the number of Tokens
matched to the Text. Not exact matches for Tokens, or if the Tokens within the
label do appear in an other order than in the text do also reduce this score.
Entities are only considered if at least one of their labels cores higher than
the minimum for all tree of <em>Min Labe Score</em>, <em>Min Text Match
Score</em> and <em>Min Match Score</em>.</li>
<li>
