In natural conversations, it is very common that a user provides background/relevant information while describing a specific scenario. Traits are specific entities, attributes, or details that the users express in their conversations. The utterance may not directly convey any specific intent, but the traits present in the utterance are used in driving the intent detection and bot conversation flows.
For example, the utterance: My flight is late and I will miss my connection because of it expresses two traits: flight delay and emergency. In this scenario, the utterance does not convey any direct intent. However, the presence of the emergency trait is used to directly assign the conversation to a human agent.
The Traits feature of the XO Platform is aimed at identifying such characteristics present in user utterances and use them for intent detection and in customizing the VA definition using these characteristics.
How Traits work
Traits are entities that can be extracted from user input, before intent recognition. They can be used in multiple scenarios
- They are involved in Indirect entity extraction, e.g.: gender or age-specific words can be inferred from the text. A phrase such as: “Seat in front of the plane with extra legroom” implies, for example, a First Class seat.
- Traits can be used for intent recognition, using rules. Any rule match for intent will be considered a definitive match.
- Traits can be identified based on keywords/phrases and their synonyms. For Example, Trait-Color: Blue – “Blue”, “Sapphire”, “Teal”; Trait-Color-Red – Red, Maroon, Crimson Trait-Status: NotWorking: “doesn’t work”, “switched off”; Trait-Status:Working: “working”, “turned on”
- Traits can also be inferred from a keyword or specific phrase in the sentence. There is no obvious association between certain words in the sentence and the value of the entity, but rather you need the sentence as a whole to determine the value. For example, Trait-Greeting-Emotion: Positive – “Good Morning”, “How are you”; Trait-Greeting-Emotion: Negative – “I hate to say”, “I am not having trouble”.
Configuring Traits involves:
- Trait Definition
- Trait Association Rules
- Trait Detection
We will discuss these in detail throughout this article, but first, let us look at a use case for traits.
A Travel Planning VA might have an added requirement to book a flight based on the cost preference.
You might have the following user utterance: I am looking for a low-cost option to London, which must result in ordering the available flights and picking the lowest-priced ticket.
This can be achieved by:
- Adding a Trait Type called Flight Fare with Trait Economy trained with the utterance low cost.
- Adding a Rule for book flight to be triggered in the presence of Economy Trait.
- Add transition conditions in case Trait Economy is present in the context.
To define Traits:
- Select the VA that you want to work with,
- Go to Build > Natural Language > Training > Traits
Following are the key features to be considered while defining Traits:
- Trait Type is a collection of related traits like Travel Class in the above example.
- Trait Type can be ML Based or Pattern Based. Each trait of a trait type can be trained using words, phrases, utterances, or patterns based on the type. Manage Trait Type allows you to define the training configuration. See below for ML-based trait configuration.
- A Trait Type can have one or more Traits.
- Traits names should be unique in a group. But traits with the same name can be present in multiple groups.
- For ML-based Traits, you can define the words, phrases, or utterances that identify the trait. One trait per trait type is detected for ML-based trait types.
- For Pattern-based Traits, you can define the patterns associated with the given trait. There is a possibility of multiple traits getting detected for pattern-based trait types. Ordering of Traits within the Trait Type signifies the importance of a trait in a trait type and detects only one trait.
- Once added, Train the assistant for the Traits to be detected from user utterances.
The ML Model for Traits
When choosing to train traits using the ML model, by default, the n-gram model is used. An n-gram is the contiguous sequence of words used from training sentences to train the model. But this might not be effective when the corpus is very less or when the training sentences, in general, contain fewer words.
From v8.0 of the platform, an option is included to skip or use the n-gram model. Further, the option to parameterize the n-gram algorithm is included.
- When the n-gram option is selected, you can configure the n-gram Sequence Length by setting the maximum value of the n-gram. It is set to 1 by default and can be configured to any integer value between 1 and 5.
- When skip-gram is selected, you can configure
- Sequence Length specifying the number of words to be included in a non-consecutive sequence. It is set to 2 by default and it can take any integer value between 2 and 4.
- Maximum Skip Distance for the number of words that can be skipped to form a non-consecutive sequence of words. This value is set to 1 by default and can take any integer value from 1 to 3.
Note: While the settings are same for all languages (in case of multilingual bot), for some languages like Chinese and Korean sequence of characters from grams and for other (Latin-based) languages are word grams.
Trait Association Rules
Trait Rules define Dialog Execution and Knowledge Graph Intent detection.
Intent detection or Dialog execution is achieved using traits, along with the ML utterances and patterns. To achieve this, intent must be associated with the required traits by adding Rules.
There are multiple ways to add rules:
- From the Traits section using the Add New Rule link.
- From the Intent Node using the Rules section under the NLP Properties.
- From the Rules tab for a given Intent, under Build > Natural Language > Training.
Each rule can have one or more conditions with AND as the operator. Multiple trait rules can be defined for a given intent and the intent is considered as a definite match if any one of the rules matches.
Knowledge Graph Intents
The Knowledge Graph can also be part of the discovery process using Traits. For this, each term or node can be associated with a trait. A given term can be associated with a single Trait.
Only one trait from a group (trait type) will be detected and is considered as a definite match.
Traits detected are included in the context object. The context is populated with unique traits identified (without reference to trait type). This information can be used in:
- Intent identification
- Dialog transition
- Entity population
- VA definitions
Batch Testing reports also include information about traits detected as do the Find Intent API.
The Ranking and Resolver gets input from the three NL engines and Traits to analyze and come up with the possible/definitive matches.
- The intent is considered as a definite match only if all the traits (one in the case of Knowledge Graph) present in a trait rule are detected.
- NL Analysis includes information on traits detected and the NLP Flow shows the information about traits detected.
The Conversation Flow is controlled using Traits. For a Dialog, Connection Rules are defined using the Trait Context. This is done from the Connection tab under the Properties Panel for the Dialog.
The Traits Context is accessed using
context.traits. It returns an array of all traits matching the intent, hence the condition to be used is ‘contains’.