Entities

In order for your bot to understand what the user said, some words of the user's utterance are more important than others. Typical examples for such important words include so-called named entities like cities or product names. One way of catching these is using entities.

What is an entity?

Each entity covers a collection of one or more words called 'entries', which all have some characteristic in common. For example, these all denote cities in the Netherlands:

Screenshot of Entity Editor for Cities in the Netherlands

In order to enhance natural understanding, the entries can have variables carrying additional information about each entry. For example, different names may denote the same city, like "Den Haag" and "The Hague". With variables it is possible to map these different variants to the same city name. Another example is the code of the nearest airport, which is useful to have in flight booking scenarios.

Screenshot of Entity Editor for Cities in the Netherlands

In the entity examples above, all entries are strings. It is also possible to have entities added as scripts where one example can be found in LUIS^Teneo. Note that entries may also consist of other entities or language objects.

How to use entities

In order to use the entity covering the cities of the Netherlands in your flow, simply add %CITIES_NETHERLANDS.ENTITY to your language condition. The variables sCity and sAirportCode can be accessed using attached scripts and data actions.

Prebuilt entities

Teneo comes with a collection of pre-built entities that are ready to be used. Some of them have been machine learned, like geographical entities like cities or adresses, while others have been hand-crafted, like a list of colors. A full list of available entities can be found here.

Create your own entities

Besides the pre-built entities, you may also create your own. See Entities for guidance. For an example of how to use them in a flow, see Extract Entities.

Was this page helpful?