GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Working with the Builder
Building a Virtual Assistant
Using Workspaces
Release Notes
Current Version
Previous Versions
Deprecations

CONCEPTS
Design
Storyboard
Dialog Tasks
Overview
Dialog Builder
Node Types
Intent Node
Dialog Node
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Group Node
Agent Transfer
User Prompts
Voice Call Properties
Dialog Task Management
Connections & Transitions
Component Transition
Context Object
Event Handlers
Knowledge Graph
Introduction
Knowledge Extraction
Build Knowledge Graph
Add Knowledge Graph to Bot
Create the Graph
Build Knowledge Graph
Add FAQs
Run a Task
Build FAQs from an Existing Source
Traits, Synonyms, and Stop Words
Manage Variable Namespaces
Update
Move Question and Answers Between Nodes
Edit and Delete Terms
Edit Questions and Responses
Knowledge Graph Training
Knowledge Graph Analysis
Knowledge Graph Import and Export
Importing Knowledge Graph
Exporting Knowledge Graph
Creating a Knowledge Graph
From a CSV File
From a JSON file
Auto-Generate Knowledge Graph
Alert Tasks
Small Talk
Digital Skills
Digital Forms
Views
Introduction
Panels
Widgets
Train
Introduction
ML Engine
Introduction
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
NLP Configurations
NLP Guidelines
Intelligence
Introduction
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Sentinment Management
Tone Analysis
Test & Debug
Talk to Bot
Utterence Testing
Batch Testing
Conversation Testing
Deploy
Channels
Publish
Analyze
Introduction
Conversations Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Meta Tags
Dashboards and Widgets
Conversation Flows
NLP Metrics
Containment Metrics
Usage Metrics
Smart Bots
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Plan & Usage
Overview
Usage Plans
Support Plans
Invoices
Authorization
Multilingual Virtual Assistants
Masking PII Details
Variables
IVR Settings
General Settings
Assistant Management
Data Table
Table Views
App Definitions
Sharing Data Tables or Views

HOW TOs
Build a Flight Status Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Web SDK Tutorial
Widget SDK Tutorial
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters

APIs & SDKs
API Reference
API Introduction
API List
API Collection
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Using the BotKit SDK

ADMINISTRATION
Introduction
Assistant Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Compliance
Using Single-Sign On
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Builder
  5. Dialog Task
  6. Entity Node

Entity Node

Virtual Assistants need to extract relevant information from the user utterance to fulfill the user intent.

Take a look at this sample utterance: Book me a flight from LA to NYC on Sunday.  To act on this user intent, which is to book a flight ticket, the VA should extract the entities such as the source city (LA), destination city (NYC), and the departure date (Sunday).

So, in a Dialog Task, for every critical data you want to get from a user utterance, you should create a corresponding entity node. You can add prompt messages to these nodes for users to input the required values.
Kore.ai supports more than 30 entity types such as Address, Airport, Quantity, and so on. You can also define the entities as a selection from a list, free-form entry, file or image attachment from a user, or as regex expressions.

Note: You need to follow one entity node with several other entity nodes to collect series of user inputs to complete a transaction, such as a username, location, amount, and due date, followed by a Webhook node to process a request to an API to complete an online transaction.

Set-Up

Setting up an entity node in a dialog task involves the following steps:

Add Node

  1. Open the dialog task to add the Entity node.
  2. Add the Entity node in the designated place. For steps in adding nodes, refer here.
  3. The Entity window is displayed with the Component Properties tab selected by default.

Configure Node

Component Properties

The Entity window allows you to configure the General Settings, User, and Error Prompts.

Note: The configurations you set up or modify in this section are reflected in all other dialog tasks that use this node.
  1. On the Component Properties tab, under the General Settings section, enter a Name and Display Name for the Entity node. Entity names cannot have spaces.
  2. From the Type drop-down list, select an entity type depending on the expected user input. For example, if you want the user to type the departure date, select Date from the drop-down. The platform does the basic validation based upon the Type selected.
    The Entity Type provides the NLP Interpreter with the expected type of data from a user utterance to enhance recognition and system performance. For more information, refer to Entity Types
  3. Based on the Type selected, you have an option to set the Entity as Multi-item thereby allowing the user multiple selections.
  4. Under the User Prompt section, enter the prompt message that you want the user to see for this entity. For example, Enter the Departure Date.
    1. You can enter channel-specific messages for user prompts using the Manage link. For more information, refer to Using the Prompt Editor.
    2. You can override the user prompt for this particular instance.
      To override,
      • Click the Settings icon on the right.
      • Enable the Override for this instance toggle. Once you enable this option, you can enter the user prompt for this particular instance. Disabling this option would delete the instance-specific prompt and revert it to the component property.
  5. Under the Error Prompts section, review the default error message, and if required, you can modify the error messages.
    1. To manage the error messages, click Manage link. For more information, refer to Using the Prompt Editor.
    2. You can override the user prompt for this particular instance.
      To override,
      • Click the Settings icon on the right.
      • Enable the Override for this instance toggle. Once you enable this option, you can enter the user prompt for this particular instance. Disabling this option would delete the instance-specific prompt and revert it to the component property.
    3. You can also reorder the error messages. To reorder,
      • Click the Settings icon on the right.
      • Enable the Present Prompts in the Order of Retries toggle. Once you enable this option, the handlebar icon would be visible before each error prompt message. You can use this to re-order the messages so that they will be displayed in that sequence.

        This image corresponds to the new dialog builder, you will find this feature in legacy builder at the same location i.e. Entity node -> Component Properties.
  6. In the Variable Namespaces section, associate the Variable Namespaces to execute this node and its transitions. This option is visible only when the Variable Namespace is enabled for the VA. You can go with the task level settings or customize it for this node. For more information, refer to Managing Namespace.
  7. In the Redaction of PII Data section, you can select the following options:
    • De-identify PII data while presenting bot responses – When this option is selected, it shows only the redacted value of the entity whenever it is used in prompts or messages.
    • Use the original value of the PII data while presenting bot responses  – When this option is selected, the redacted value of the entity is used in prompts or messages.
      Note: The PII data settings are applied for messages or user prompts that are added in Plain Text (Simple mode) as well as JavaScript code (Advanced mode).

      Important Notes:

    • The PII information is always redacted/masked in the Chat History, messages, prompts and all other components irrespective of the option selected.
    • By default, the PII Redaction option is turned-off for all entities. To learn how to enable the PII redaction option. Learn more.

     

Instance Properties

Use the Instance Properties to determine whether to make the entity value mandatory as well as to choose if you want to consider values from previous user utterances to capture entities.

Note: The settings in the Instance Properties tab are specific to the current dialog task and do not reflect in the other dialog tasks that use this entity node.
  1. On the Entity window, click the Instance Properties tab.
  2. Under the User Input section, select an option (Refer to the below section for how the entity flow is managed):
    • Mandatory: This entity is required, and users must provide a valid entry before proceeding with the dialog flow. A prompt is displayed for the user to resolve in case ambiguous values for the entity are detected in the user utterance.
      You can configure the number of times the user would be prompted for this entity value by setting the number of Allowed Retries to any value between 1 and 5, the default being 5.
      Further, you can define the VA Behavior on Exceeding Retries, this can be set to trigger End of Dialog or Transition to a Node. This would result in the creation of a Connection Rule called Behavior on Exceeding Retries. The message displayed to the user on exceeding retries can be customized from the Standard Responses, refer here.
    • Optional: The user is prompted only once for this entity and the system proceeds with any input provided by the user. In case ambiguous values for these optional entities are detected in the User Utterance, then a resolution prompt is displayed allowing the user to pick the correct value.
      You can set a value under the Default Value field. This value would be assigned to this entity when the task execution reaches this entity and the user does not provide any value when prompted and if no value is available from previous utterances.
    • Hidden: If enabled, the VA will not prompt for the entity value. The value would be considered if explicitly provided by the user in previous utterances.
      You can set a value under the Default Value field. This value would be assigned to this entity when the task execution reaches this entity and no value is available from previous utterances.
  3. User Input Correction section (v7.3) to define whether the user input needs to be auto-corrected. This option is available only for string type entities. The two options are listed below:
    • Auto-correct user input is the default setting. The platform builds a custom dictionary for each VA to include all synonyms, task names, pattern words, and small talk utterance words on top of a standard dictionary. This feature is not supported in all languages, Click here for details.
    • Do not auto-correct user input
      To ensure backward compatibility, the following settings are applied to existing bots (migrating VAs older than v7.3 to v7.3):

      Old State (Entity Extraction) New State (User Input Correction)
      Evaluate unused text from previous utterances. Do not auto-correct user input.
      Evaluate unused text and text used for extracting entities from previous utterances. Do not auto-correct user input.
      Do not evaluate previous utterances and explicitly prompt the user – Do not auto-correct [Enabled]. Do not auto-correct user input.
      Do not evaluate previous utterances and explicitly prompt the user – Do not auto-correct [Disabled]. Auto-correct user input.
  4. Under the Entity Extraction section, select one of these options:
    • Evaluate the unused text from the previous utterance: When this option is selected, the entity uses the text that was not used by any other entity in the dialog so far. This is the default option.
    • Evaluate the unused text and text used for extracting entities from previous utterances: Select this option if you want to reuse an entity value extracted by another entity node in the dialog.
    • Do not evaluate previous utterances and explicitly prompt the user: Select this option if you want the VA to ignore the previous user utterances and explicitly prompt the user to provide value for the entity.
      • Further, you can restrict the platform from reusing the input provided for this entity to extract any other entities by selecting the Do not reuse option.
  5. Under the Entity Rules section, you can configure rules to validate the user input.
  6. Click the Advanced Controls to set up these options:
    • Intent Detection (Applies only to String and Description entities): Select one of these options to determine the course of action if the VA encounters an entity as a part of the user entry for the String or Description entities:
      • Accept input as entity value and discard intent detected: The VA captures the user entry as a string or description and ignores the intent.
      • Prefer user input as intent and proceed with Hold & Resume settings: The user input is considered for intent detection and proceed according to the Hold & Resume settings.
      • Ask the user how to proceed: Allow the user to specify if they meant intent or entity.
    • Interruptions Behavior: To define the interruption handling at this node. You can select from the below options:
      • Use the task level ‘Interruptions Behavior’ setting: The bot refers to the Interruptions Behavior settings set at the dialog task level.
      • Customize for this node option: You can customize the Interruptions Behavior settings for this node by selecting this option and configuring the same.  Read the Interruption Handling and Context Switching article for more information.
    • Precedence (Applies to all Entity types except String and Description nodes): When the user’s input for an entity consists of a valid value for the entity and another intent, you can control the experience by choosing between Intent over Entity or Entity over Intent options. For example, if a Flight Booking virtual assistant prompts for the destination and the user enters, Bangalore, how’s the weather there? you get to define how the VA responds in such cases; pick the entity and add the intent to the Follow-up Intents stack or go ahead with the intent first based upon the Interruptions Behavior settings.
    • Custom Tags: It defines tags to build custom profiles of your VA conversations. Click here for more.

User Input Flow

When a user is prompted for input, the following is the process performed by the platform:

  • If the user responds with a valid value, then the entity populates with that value and the dialog flow continues.
  • If ambiguous values are identified in the user response, then an ambiguity resolution prompt is displayed.
  • If the user responds with an invalid utterance i.e. an utterance that does not contain a valid input for the ambiguity resolution, then:
    • If the given value is valid for the entity (any possible value for the entity), it is used for the entity and the conversation is continued.
    • If the given value is not valid for the entity and if the value triggers any task intent, faq, or small talk, then:
      • The intent is executed as per hold and resume settings and when (and if) the dialog (containing the entity) is resumed, the user is prompted for the entity value.
      • If the value does not trigger any task intent, faq, or small talk, the entity is left blank and the conversation is continued from the entity’s transitions.
  • If the user exceeds the retry limit, the behavior defined for exceeding retries would be triggered. Note that if this is a child task and the behavior is set to end the dialog then the parent task would also be terminated.

NLP Properties

  1. On the NLP Properties tab, under the Suggested Synonyms for the < entity name > section, enter synonyms for your entity.
  2. Click Enter after each entry to save it. For more information, refer to Managing Synonyms.
  3. Under the Suggested Patterns for < entity name > section, click + Add Pattern to add new patterns for your entity. The Patterns field is displayed. For more information, refer to Managing Patterns.
  4. Under the Manage Context section, in the Context Output field, define the context tags to be set in the context when this entity populates.
  5. You can select Auto emits the entity values captured option as part of the Context Object.

(Click here for Context Management)

IVR Properties

You can use this tab to define the input mode, grammar, prompts, and call behavior parameters for this node to use in IVR Channel. You can define this at the node level. Click here for details.

Connections Properties

From the node’s Connections tab, you can determine which node in the dialog task to execute next. You can write the conditional statements based on the values of any Entity or Context Objects in the dialog task, or you can use intents for transitions.
To setup Component Transitions, follow the below steps:

  1. Under the Connection Rules section, from the Default drop-down list, you can select a node.
  2. To configure a conditional flow, click Add IF.
  3. In case you have enabled the Behavior on Exceeding Entity Retries in the Instance Properties, you would see the Behavior on Exceeding Entity Retries connection rule here.
  4. Configure the conditional expression based on one of the following criteria:
    1. Entity: Compare an Entity node in the dialog with a specific value using one of these operators: Exists, Does not Exist, equals to, greater than equals to, less than equals to, not equal to, greater than, and less than. Select the entity, operator using the respective drop-down lists, and type the number in the Value box. For example, PassengerCount (entity) greater than (operator) 5 (specified value).
    2. Context: Compare a context object in the dialog with a specific value using one of these operators: Exists, Does not Exist, equals to, greater than equals to, less than equals to, not equal to, greater than, and less than. For example, Context.entity.PassengerCount (Context object) greater than (operator) 5 (specified value).
    3. Intent: Select an intent that matches the next user utterance.
  5. From the Then go to the drop-down list, select the next node to execute in the dialog flow if the conditional expression succeeds. For example, if the PassengerCount (entity) greater than (operator) 5 (specified value), Then go to Offers (sub-dialog).
  6. In the Else drop-down list, select the node to execute if the condition fails.
Note: If you want to write multiple If conditions, click Add Else If below the last If conditional expression.
Menu