Author: buildbot
Date: Tue Nov 11 10:01:49 2014
New Revision: 928728
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/lucenefstlinking.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 11 10:01:49 2014
@@ -1 +1 @@
-1638049
+1638058
Modified:
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.html
==============================================================================
---
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.html
(original)
+++
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.html
Tue Nov 11 10:01:49 2014
@@ -166,12 +166,12 @@ Configurations can be created by using t
<h4 id="linking-mode">Linking Mode</h4>
-<p>The FST linking engine does support three linking modes. Those are
configures using the <strong>Linking Mode</strong>
<em>(enhancer.engines.linking.lucenefst.mode)</em> property.</p>
-<p><img alt="Linking Mode Configuration"
src="fstengine-config-indexlayout.png" /></p>
-<p>The three modes are</p>
+<p>The FST linking engine does support two different linking modes. Those are
configures using the <strong>Linking Mode</strong>
<em>(enhancer.engines.linking.lucenefst.mode)</em> property.</p>
+<p><img alt="Linking Mode Configuration"
src="fstengine-config-linkingmode.png" /></p>
+<p>The two modes are</p>
<ol>
-<li><code>PLAIN</code>: This mode links all words in the parsed text. This
mode does not require any NLP processing as the Solr Analyzer for the
configured field will be used for processing the text. The basic mode is best
if the vocabulary contains entities that appear in text with tokens other than
nouns (e.g. a vocabulary that contains activities)</li>
-<li><code>LINKABLE_TOKEN</code>: This mode will use the provided <a
href="#text-processing-configuration">Text Processing Configuration</a>. This
is a good default for vocabularies that contain entities mentioned in texts as
Nouns and/or ProperNouns.
+<li><code>PLAIN</code>: This mode links the plain text with the vocabulary.
Every single word of the text will get looked up with the vocabulary. This mode
does not use NLP results other than language detection. This mode also ot make
use of the <a href="#text-processing-configuration">Text Processing
Configuration</a>. The PLAIN mode works fine with smaller and specific
vocabularies that do not only contain entities but also things like product
ids, activities, adjectives ...</li>
+<li><code>LINKABLE_TOKEN</code>: This mode links only linkable tokens of the
parsed text. The provided <a href="#text-processing-configuration">Text
Processing Configuration</a> is used to determine linkable tokens in the text
(based on NLP results). This is the default mode for this engine. It is well
suited for vocabularies containing named entities (such as persons, cities,
products, organizations, roles, ...)
<!-- 3. <code>NER</code>: This mode will only consider detected Named Entities
for linking. This mode is similar to using the <a
href="namedentitytaggingengine">Named Entity Linking Engine</a>. This is a best
mode if the enhancement chain contains an NER component that can detect the
types of entities contained in the linked vocabulary. --></li>
</ol>
<p>By default the FST linking engine uses the <code>LINKABLE_TOKEN</code>. In
this mode this engine behaves similar as the <a
href="entityhublinking">Entityhub Linking Engine</a>.</p>
