You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Example utterances are text examples of user questions or commands. To teach Language Understanding (LUIS), you need to add example utterances to an intent.
37
+
Example utterances are text examples of user questions or commands. To teach Language Understanding (LUIS) when to predict this intent, you need to add example utterances to an intent. LUIS needs in the range of 15 to 30 example utterances to begin understanding the intent. Do not add example utterances in bulk. Each utterance should be carefully chosen for how it is different than examples already in the intent.
35
38
36
-
1. On the **GetEmployeeInformation**intent details page, enter a relevant utterance you expect from your users, such as `Does John Smith work in Seattle?` in the text box below the intent name, and then press Enter.
39
+
1. On the intent details page, enter a relevant utterance you expect from your users, such as `Deliver a large cheese pizza` in the text box below the intent name, and then press Enter.
37
40
38
-
41
+
> [!div class="mx-imgBorder"]
42
+
> 
39
43
40
-
LUIS converts all utterances to lowercase and adds spaces around tokens such as hyphens.
44
+
LUIS converts all utterances to lowercase and adds spaces around [tokens](luis-language-support.md#tokenization) such as hyphens.
An example utterance in an intent might have an intent prediction error between the intent the example utterance is currently in and the prediction intent determined during training.
50
+
An example utterance in an intent might have an intent prediction error between the intent the example utterance is currently in and the intent determined during training.
47
51
48
-
To find utterance prediction errors and fix them, use the **Filter**option's **Evaluation**options of Incorrect and Unclear combined with the **View** option of **Detailed view**.
52
+
To find utterance prediction errors and fix them, use the **Filter** options of Incorrect and Unclear combined with the **View** option of **Detailed view**.
49
53
50
54
51
55
52
56
When the filters and view are applied, and there are example utterances with errors, the example utterance list shows the utterances and the issues.
53
57
54
-
](./media/luis-how-to-add-intents/find-errors-in-utterances.png#lightbox)
58
+
> [!div class="mx-imgBorder"]
59
+
> ](./media/luis-how-to-add-intents/find-errors-in-utterances.png#lightbox)
55
60
56
61
Each row shows the current training's prediction score for the example utterance, the nearest rival's score, which is the difference in these two scores.
57
62
58
63
### Fixing intents
59
64
60
65
To learn how to fix intent prediction errors, use the [Summary Dashboard](luis-how-to-use-dashboard.md). The summary dashboard provides analysis for the active version's last training and offers the top suggestions to fix your model.
61
66
62
-
## Add a custom entity
63
-
64
-
Once an utterance is added to an intent, you can select text from within the utterance to create a custom entity. A custom entity is a way to tag text for extraction, along with the correct intent.
65
-
66
-
See [Add entity to utterance](luis-how-to-add-example-utterances.md) to learn more.
67
-
68
-
## Entity prediction discrepancy errors
69
-
70
-
The entity is underlined in red to indicate an [entity prediction discrepancy](luis-how-to-add-example-utterances.md#entity-status-predictions). Because this is the first occurrence of an entity, there are not enough examples for LUIS to have a high-confidence that this text is tagged with the correct entity. This discrepancy is removed when the app is trained.
71
-
72
-
73
-
74
-
The text is highlighted in blue, indicating an entity.
75
-
76
-
## Add a prebuilt entity
77
-
78
-
For information, see [Prebuilt entity](luis-how-to-add-entities.md#add-a-prebuilt-entity-to-your-app).
79
-
80
67
## Using the contextual toolbar
81
68
82
-
When one or more example utterances are selected in the list, by checking the box to the left of an utterance, the toolbar above the utterance list allows you to perform the following actions:
83
-
84
-
* Reassign intent: move utterance(s) to different intent
85
-
* Delete utterance(s)
86
-
* Entity filters: only show utterances containing filtered entities
87
-
* Show all/Errors only: show utterances with prediction errors or show all utterances
88
-
* Entities/Tokens view: show entities view with entity names or show raw text of utterance
89
-
* Magnifying glass: search for utterances containing specific text
90
-
91
-
## Working with an individual utterance
92
-
93
-
The following actions can be performed on an individual utterance from the ellipsis menu to the right of the utterance:
94
-
95
-
* Edit: change the text of the utterance
96
-
* Delete: remove the utterance from the intent. If you still want the utterance, a better method is to move it to the **None** intent.
97
-
* Add a pattern: A pattern allows you to take a common utterance and mark replaceable text and ignorable text, thereby reducing the need for more utterances in the intent.
69
+
The context toolbar provides other actions:
98
70
99
-
The **Labeled intent** column allows you to change the intent of the utterance.
71
+
* Edit or delete example utterance
72
+
* Reassign example utterance to a different intent
73
+
* Filters and views: only show utterances containing filtered entities or view optional details
74
+
* Search through example utterances
100
75
101
76
## Train your app after changing model with intents
102
77
103
-
After you add, edit, or remove intents, [train](luis-how-to-train.md) and [publish](luis-how-to-publish-app.md) your app so that your changes are applied to endpoint queries.
78
+
After you add, edit, or remove intents, [train](luis-how-to-train.md) and [publish](luis-how-to-publish-app.md) your app so that your changes are applied to endpoint queries. Do not train after every single change. Train after a group of changes.
0 commit comments