An entity is a unit of the NLU core of CAILA. An entity is a sequence of words linked by an intent or rule. For example: names, date and time, location, etc.
\nCAILA offers the following to the developer:
\nAll entities found in a phrase will be available in the script via the variable $jsapi.context().entities or $entities.
For example:
\n state:\n q!: Information about product *\n a: Information about product: {{ $entities[0].value }}Entities can be used in intents.
\nMore details about filling in slots in intents and the Slot filling process
\nWhen the intent is activated, the data of the respective slot will be written to the variable $parseTree._<slot name>.
The initial text for which a match has been found will be written to this variable; alternatively, the DATA specified for this entity in the entity editor will be written to this variable.
For example:
\n state:\n intent: /bye\n a: Action: {{ $parseTree._Action }}, Product: {{ $parseTree._Product }}\n\n state:\n intent: /sell\n a: Action: {{ $parseTree._Action }}, Product: {{ $parseTree._Product }}You can use entities in patterns by referencing them as @<entity name> or @<entity name>::<slot name>.
For an entity specified in a pattern, a slot is created automatically and the entity is included in the $parseTree.
The value of the entity will be available in the script as $parseTree._<slot name>.
For example:
\n state:\n q!: * @Product::p1 *\n a: Information about product: {{ $parseTree._p1 }}You can also use converters in entities. First, you need to define an entity through a named pattern using the patterns tag, and then declare a converter in it. For example:
patterns:\n $four = @four || converter = function() {return 4}In this example we created @four entity, in which we declared converter. The converter function returns 4.
You can use entities in the phrase examples of STS classifier by referencing them as @<entity name> or @<entity name>::<slot name>.
For the entity specified in the example, a slot is automatically created and the entity is included in the $parseTree.
The value of the entity will be available in the script as $parseTree._<slot name>.
For example:
\n state:\n e!: @Pizza::p2\n a: Information about pizza: {{ $parseTree._p2 }}In JAICP entities can refer to other entities.
\nLet's have a look at entities behavior when:
\n\nLet's have a look at how the client's address fills in the entities. The address consists of two parts: street and house number.
\nGo to the CAILA > Entities > My entities tab on the control panel. Create the following entities:
\nstreet_name with patterns:Main\nWeststreet with a pattern:@street_name streetNow let's create a address entity. It refers to the street entity and the @duckling.number system entity:
@street @duckling.numberNow let's say the client enters the message Main Street. The Value field is filled in the following way:
\nMain in the street_name entity;Main street in the street entity.If the client enters the message Main Street 15, then Value fills in as follows:
\nMain in the street_name entity;Main street in the street entity;Main Street 15 in the address entity.Let's say we have our own online store that sells groceries. We will use the entities to specify from the client's request what kind of fruits and vegetables they want to buy.
\nGo to the CAILA > Entities > My entities tab on the control panel. Create the following entities:
\nfruit with patterns:apple\nbanana\nlimevegetable with patterns:potato\ntomato\ncucumberIn addition, specify values name and type in the DATA field for each pattern that will correspond to the name and type of the product. In the DATA field, you can add any information in JSON format that may be needed in the script.
For example, for the pattern banana specify:
{\n \"name\": \"banana\",\n \"type\": \"fruit\"\n}Do the same for each pattern of the vegetable entity. For instance:
{\n \"name\": \"potato\",\n \"type\": \"vegetable\"\n}Now, let's combine these entities into the grocery entity. Create an entity grocery and specify the patterns @vegetable and @fruit in the Dictionary field.
For example, the client writes the message Potato. The DATA field of the Let us consider a situation where we have multiple matches for an entity search query. Create a All the values of the entity must be in the Use the CAILA API method: Add a parameter for the The state: Start\n q!: $regex</start>\n a: Hello! Our store offers a wide range of vegetables and fruit. What would you like to order?\n\n state: Grocery\n q!: * @grocery *\n script:\n $reactions.answer(\"The name of the product: {{ $parseTree._grocery.name }}\");\n $reactions.answer(\"The type of the product: {{ $parseTree._grocery.type }}\");grocery entity will be filled with the information specified in the DATA field of the vegetable entity. Because the entity grocery contains the entity vegetable the message will be recognized by both these entities. In a result, the bot will send the following:The name of the product: potato\nThe type of the product: vegetableFilling the $entities array
\n@City custom entity. Add the two values of South Carolina and North Carolina to the entity’s reference list. If a client requests Carolina, the bot must prompt to specify which city the client means.$entities array.PUT /cailapub/api/caila/p/{accessToken}/entities/{entityId}@City entity:{\n \"fuzzySearch\": true // can be used to find multiple values and add them to the array.\n}$context.entities array will now contain the list with the South Carolina and North Carolina values, and the bot may prompt the client to specify the city.