Page History

...

...

...

...

...

...

...

...

...

...

...

• Tokens marked with this flags will be ignore by this stage, and no process will be performed.

...

• Tokens need to have all the specified flags, in order to be processed

...

• Enable all debug log functionality of the stage, if any.

...

"

...

language":"en",

...

...

"

...

breakers":

...

";"

...

...

V

...

------------[

...

Lorem ipsum sit amet, consectetur adipisci. Sed luctus lorem. Cras nec ultricies nulla. Maecenas porta cursus; massa non consectetur.]-------------

...

V  
^--[

...

Lorem ipsum sit amet, consectetur adipiscing]--V--[

...

Sed luctus lorem]--V--[

...

Cras nec ultricies nulla]--V--[

...

Maecenas porta cursus]--V--[

...

massa non consectetur]--^  

...

Vertex Flags:

...

...

• The current maximum size of a text block is 64K characters.
• Text blocks larger than this will be arbitrarily split, and the vertex will be marked with "OVERFLOW_SPLIT"\

...

Resource Data

Description of resource.

Resource Format

The only file which is absolutely required is the entity dictionary. It is a series of JSON records, typically indexed by entity ID.

Description of entity:
Entity JSON Format

{
  "id":"Q28260",
  "tags":["{city}", "{administrative-area}", "{geography}"],
  "patterns":[
    "Lincoln", "Lincoln, Nebraska", "Lincoln, NE"
  ],
  "confidence":0.95
  
  . . . additional fields as needed go here . . . 
}

Notes

1. Multiple entities can have the same pattern.
   1. If the pattern is matched, then it will be tagged with multiple (ambiguous) entity IDs.
2. Additional fielded data can be added to the record
   1. As needed by downstream processes.

Fields

• id (required, string) - Identifies the entity by unique ID. This identifier must be unique across all entities (across all dictionaries).
  • Typically this is an identifier with meaning to the larger application which is using the Language Processing Toolkit.
• tags (required, array of string) - The list of semantic tags which will be added to the interpretation graph whenever any of the patterns are matched.
  • These will all be added to the interpretation graph with the SEMANTIC_TAG flag.
  • Typically, multiple tags are hierarchical representations of the same intent. For example, {city} → {administrative-area} → {geographical-area}
• patterns (required, array of string) - A list of patterns to match in the content.
  • Patterns will be tokenized and there may be multiple variations which can match.
    • NOTE:  Currenty, tokens are separated on simple white-space and punctuation, and then reduced to lowercase.
    • TODO:  This will need to be improved in the future, perhaps by specifying a pipeline to perform the tokenization and to allow for multiple variations.
• confidence (optional, float) - Specifies the confidence level of the entity, independent of any patterns matched.
  • This is the confidence of the entity, in comparison to all of the other entities. Essentially, the likelihood that this entity will be randomly encountered.

Other, Optional Fields

...

...