Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Preparing data for intent detection

Updated on March 11, 2021

In the Lexicon selection step, provide a sentiment lexicon and a list of intent types, together with words or phrases that are specific to each intent type that yo want to detect.

  1. In the Lexicon drop-down list, select a sentiment lexicon that you want to use in the model building process.
    A sentiment lexicon provides the list of features that are used in sentiment analysis and intent detection. You can use the default lexicon based on the pySentimentLexicon rule provided by Pega. For more information, see Sentiment lexicons.
  2. Define the intent types that you want to detect by performing the following actions:
    1. In the Intent config selection section, click Add item.
    2. In the Intent field, enter the name of the intent type, for example, Purchase.
    3. In the Action field, enter verbs or verb phrases that describe the user ideas or actions with regard to the intent type, for example, buy, purchase, want to acquire, intend to order, need to purchase, and so on.
    4. In the Subject field, enter any domain-specific words or phrases (for example, nouns or noun phrases) that relate to the intent type that you specified, for example, laptop, new phone, service, internet plan, and so on.
  3. Click Next.
  • Previous topic Setting up an intent detection model
  • Next topic Uploading data for training and testing of the intent detection model

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us