Page History

...

The new patterns can be formed by previously defined tags and text literals. For example, the pattern "{name} likes {product}" where "{name}" and "{product}" are tags and "likes" is the text literal. Since this stage allows for complex entity tagging, is also know as the "Advance Recognizer".

...

• SEMANTIC_TAG - Identifies all lexical items which are semantic tags.
• PROCESSED - Placed on all the tokens which composed that compose the semantic tag.

Vertex Flags:

...

Resource Data

The resource data will be a database of advanced patterns, and the resulting semantic tag which that they produce.

Resource Format

The pattern database is a series of JSON records, typically indexed by "pattern block ID". Each JSON record represents an a block of patterns (one or more) which that all produce the same semantic tag. The format is as follows:

...

• Parameter
  summary Identifies the entry. This identifier may not be unique, and is not the id of the database, but an specific use case id name id required true

  
  
  • Typically, this is an identifier with meaning to the larger application which that is using the Language Processing Toolkit.

• Parameter
  summary What to show the user when browsing this entity name display required true

• Parameter
  summary Tag which will identify any match in the graph, as an interpretation name tag required true

  • These will all be added to the interpretation graph with the SEMANTIC_TAG flag.

  • Tip
    Tags are hierarchical representations of the same intent. For example, {city} → {administrative-area} → {geographical-area}

• Parameter
  summary Pattern to match in the content name pattern required true

  • Note
    Currently, tokens are separated on simple white-space and punctuation, and then reduced to lowercase.

• Parameter
  summary Specifies the confidence level of the entry, independent of any patterns matched name confidence type boolean required true

  • This is the confidence of the entry, in comparison to all of the other entries. (Essentially, the likelihood that this entity will be randomly encountered.)

• Parameter
  summary Additional information for the entry. At the moment this information is not expected default empty json name fields type json

• Parameter
  summary Date in milliseconds of the last time the entry was updated name updatedAt type date epoch required true

• Parameter
  summary Date in milliseconds of the creation time of the entry name createdAt type date epoch required true