{ "componentChunkName": "component---src-templates-doc-page-js", "path": "/docs/en/NLU_core/slot_filling/", "result": {"data":{"site":{"siteMetadata":{"title":"Gatsby-doc-engine"}},"markdownRemark":{"id":"cdd59e1c-5861-562a-af2b-e984659524cb","excerpt":"Slot Filling Slot Filling is a process of requesting additional data in order to fulfill the client request. The data acquired during an additional data request…","html":"

Slot Filling

\n
\n

Slot Filling is a process of requesting additional data in order to fulfill the client request. The data acquired during an additional data request are available for use in the script.

\n

Slots are the data that the client sends with a request or when additional data are requested. Each slot has required attributes: Name, Type.

\n
\n

Filling slots from a request

\n

More details about slot filling in the interface

\n

If we regard the intent as a function that the client can call, then a slot is a variable or a parameter of this function.

\n

For example, for the /Weather intent, an example phrase can be \"Weather in London today\" and the two slots, City and Date. In this example, London will be placed in the City slot and the current date will be placed in the Date slot.

\n

Here, all filled slots will be passed into the script in the variable $parseTree._<SlotName>. The associated value will be stored in the variable, and text will be included if there is no associated value.

\n

The filled slots are used in the script as follows:

\n
    state:\n        intent!: /Weather\n        a: The weather in {{ $parseTree._City }} on {{ $parseTree._Date }}
\n
\n
The Type attribute
\n

Each slot must have a Type that corresponds to the entity Type = entity. This type defines the type of the data that will be placed into the slot. You can use both system and custom entities.

\n

For example, for the Date slot with the type @zb.datetime: the word \"today\" from a client request will be passed to the entity @zb.datetime and will be placed into the Date slot.

\n

If there are multiple slots of the same type in the intent, then they will be filled in sequentially.

\n

If you need to handle an arbitrary amount of slots of one type in a request or to handle variables with different entity types, use the $entities structure into which all found entities will be passed in their initial form.

\n
\n
The Required attribute
\n

Each slot has a Required attribute:

\n\n

Before you start the slot filling process, familiarize yourself with slot filling in more detail.

\n
\n
Arrays in slots
\n

You need to have an array in the filled $parseTree._<SlotName> slot to process requests with duplicate entities.

\n

Enable the Is Array switch to have all the entities placed into this slot in the form of an array:

\n

\n You can exit the slot filling script only by answering all the questions or by using the /start command.

\n

Consider the following script:

\n
    state:\n        intent!: /Weather\n        a: The weather in {{ $parseTree._City }} on {{ $parseTree._Date.value }}
\n

In this case, we have filled all the slots as follows:

\n

\n \n \n

\n

Here @City is a custom entity where we have specified all the cities for which we can provide weather forecasts.

\n

Client requests:

\n
    \n
  1. The weather in Moscow for tomorrow: the slots are filled and the bot will provide an answer right away.
    2. \n
  2. The weather for tomorrow: the City slot is empty so clarifying questions will be asked. As soon as a correct answer is given, the control will be passed to the script and the bot will give a reply.
    3. \n
  3. The weather in Moscow: the Date slot is empty so clarifying questions will be asked. As soon as a correct answer is given, the control will be passed to the main function and the bot will give a reply.
    4. \n
\n
\n

Interruption of slot filling

\n

You can configure slot interruption conditions in the chatbot.yaml file in the injector section:

\n
injector:\n    slotfilling:\n        maxSlotRetries: 1\n        stopOnAnyIntent: true\n        stopOnAnyIntentThreshold: 0.2
\n

The following parameters are available here:

\n\n
Interruption by intent
\n

If stopOnAnyIntent: true and an intent whose confidence parameter is greater than stopOnAnyIntentThreshold matches the client request, then slot filling will be interrupted by intent.

\n

The confidence parameter is the degree of confidence that the JAICP platform has that the input phrase is related to the specified intent.

\n

Note that it is important to take the starting context of the slot filling into consideration. For example, if on interruption it is not possible to reach the state with the respective intent (for example, the tag intent is not global), then the request will result in event!: noMatch.

\n

If the interruption parameters are not specified in the chatbot.yaml configuration file, then slot filling will be interrupted according to the default parameters:

\n
injector:\n    slotfilling:\n        maxSlotRetries: 2\n        stopOnAnyIntent: false\n        stopOnAnyIntentThreshold: 0.2
","frontmatter":{"title":"","description":null},"headings":[{"value":"Slot Filling"}]}},"pageContext":{"slug":"/docs/en/NLU_core/slot_filling/","previous":{"fields":{"slug":"/docs/en/NLU_functions/NLU_functions/"},"frontmatter":{"title":"","description":null}},"next":{"fields":{"slug":"/docs/en/NLU_core/rule_activation/"},"frontmatter":{"title":"","description":null}}}}, "staticQueryHashes": ["1209419333"]}