This is an automated email from the ASF dual-hosted git repository.

sergeykamov pushed a commit to branch NLPCRAFT-513
in repository https://gitbox.apache.org/repos/asf/incubator-nlpcraft-website.git


The following commit(s) were added to refs/heads/NLPCRAFT-513 by this push:
     new 33e4f1b  WIP.
33e4f1b is described below

commit 33e4f1bf288ed833084937a58043af545c2c8da6
Author: Sergey Kamov <[email protected]>
AuthorDate: Thu Jan 12 22:56:47 2023 +0400

    WIP.
---
 built-in-entity-parser.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/built-in-entity-parser.html b/built-in-entity-parser.html
index 0257551..aceaf0c 100644
--- a/built-in-entity-parser.html
+++ b/built-in-entity-parser.html
@@ -225,14 +225,14 @@ id: built-in-entity-parser
 
             <p>
                 Each {% scaladoc nlp/parsers/NCSemanticElement 
NCSemanticElement %}
-                is presented by <code>id</code>, <code>groups</code>, 
<code>synonyms</code>, <code>values</code> and <code>properties</code>.
+                is presented by <code>type</code>, <code>groups</code>, 
<code>synonyms</code>, <code>values</code> and <code>properties</code>.
             <p>
                 <span id="synonyms" class="section-sub-title">Synonyms <a 
href="#"><i class="top-link fas fa-fw fa-angle-double-up"></i></a></span>
             <p>
                 NLPCraft uses fully deterministic named entity recognition and 
is not based on statistical approaches that
                 would require pre-existing marked up data sets and extensive 
training. For each semantic element you can either provide a
                 set of synonyms to match on or specify a piece of code that 
would be responsible for detecting that named
-                entity (discussed below). A synonym can have one or more 
individual words. Note that element's ID is its
+                entity (discussed below). A synonym can have one or more 
individual words. Note that element's type is its
                 implicit synonym so that even if no additional synonyms are 
defined at least one synonym always exists.
                 Note also that synonym matching is performed on 
<em>normalized</em> and <em>stemmatized</em> forms of both
                 a synonym and user input on first phase and if first attempt 
is not successful, it tries to match <em>stemmatized</em> forms
@@ -359,7 +359,7 @@ id: built-in-entity-parser
             <p>
                 Each semantic element always belongs to one or more groups. 
Semantic element provides its groups via
                 {% scaladoc nlp/parsers/NCSemanticElement getGroups() %} 
method.
-                By default, if element group is not specified, the element ID 
will act as its default group ID.
+                By default, if element group is not specified, the element 
type will act as its default group.
                 Group membership is a quick and easy way to organise similar 
semantic elements together and use this
                 categorization in <a href="/intent-matching.html">IDL</a> 
intents.
             </p>
@@ -629,7 +629,7 @@ id: built-in-entity-parser
                         )
                         List(
                             new NCSemanticElement():
-                                override def getId: String = "time"
+                                override def getType: String = "time"
                                 override def getSynonyms: Set[String] = 
Set("{&lt;CUR&gt;|_} &lt;TIME&gt;", "what &lt;TIME&gt; {is it now|now|is it|_}" 
)
                         )
                     ).build
@@ -662,7 +662,7 @@ id: built-in-entity-parser
                   "&lt;CUR&gt;": "{current|present|now|local}"
                   "&lt;TIME&gt;": "{time &lt;OF&gt; day|day 
time|date|time|moment|datetime|hour|o'clock|clock|date time|date and time|time 
and date}"
                 elements:
-                  - id: "x:time"
+                  - type: "x:time"
                     description: "Date and/or time token indicator."
                     synonyms:
                       - "{&lt;CUR&gt;|_} &lt;TIME&gt;"

Reply via email to