You can create your own entities for your agent through web forms, uploading them in JSON or CSV formats, or via API calls.
Developer entities can and should be used for anything that's not covered by system entities, and should contain values you expect from your users. Like training phrases, the more entities you provide, the more your agent will understand.
These entities allow for the mapping of synonyms to a reference value. For example, a food type entity could have an entry with a reference value of "vegetarian" with synonyms of "veg" and "veggie".
Dev mapping entities have the checkbox Define synonyms checked, and reference values and synonyms are added to each row.
Enum type entities contain a set of entries that do not have mappings to reference values. Entries can contain simple words or phrases or other entities.
Enum type entities have the Define synonyms option unchecked and add single value rows.
When a developer enum entity contains other entities as aliases (using the
@entityname syntax), it's called a composite entity. Composite entities are most useful for describing objects or concepts that can have several different attributes.
For example, a robot's movement can have two characteristics: direction and number of steps. In order to describe all possible combinations, an entity that captures the direction needs to be created:
@move entity refers to the direction entity and uses its alias and the number of steps. Since this is a developer enum entity type, Define synonyms needs to be unchecked.
By providing the example "Move 10 steps forward", the
@move entity is annotated automatically.