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
Copy file name to clipboardExpand all lines: articles/cognitive-services/LUIS/tutorial-entity-roles.md
+13-19Lines changed: 13 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,14 @@
1
1
---
2
2
title: "Tutorial: Contextual data with roles - LUIS"
3
-
titleSuffix: Azure Cognitive Services
4
3
description: Find related data based on context. For example, an origin and destination locations for a physical move from one building and office to another building and office are related.
5
-
services: cognitive-services
6
-
author: diberry
7
-
manager: nitinme
8
-
ms.custom: seodec18
9
-
ms.service: cognitive-services
10
-
ms.subservice: language-understanding
11
4
ms.topic: tutorial
12
-
ms.date: 12/17/2019
13
-
ms.author: diberry
5
+
ms.date: 03/30/2020
14
6
#Customer intent: As a new user, I want to understand how and why to use roles on an entity.
15
7
---
16
8
17
9
# Tutorial: Extract contextually related data from an utterance
18
10
19
-
In this tutorial, find related pieces of data based on context. For example, an origin and destination locations for a transfer from one city to another. Both pieces of data may be required and they are related to each other.
11
+
In this tutorial, find related pieces of data based on context. For example, origin and destination locations for a transfer from one city to another. Both pieces of data may be required and they are related to each other.
20
12
21
13
A role can be used with any prebuilt or custom entity type, and used in both example utterances and patterns.
22
14
@@ -45,24 +37,26 @@ A role should be used when the entity data to extract:
45
37
46
38
## Create a new app
47
39
48
-
1. Sign in to the preview LUIS portal with the URL of [https://preview.luis.ai](https://preview.luis.ai).
40
+
1. Sign in to the [LUIS **preview** portal](https://preview.luis.ai).
49
41
50
-
1. Select **Create new app**, enter the name `HumanResources` and keep the default culture, **English**. Leave the description empty.
51
-
52
-
1. Select **Done**.
42
+
1. Select **+ New app for conversation**, enter the name `HumanResources` and keep the default culture, **English**. Leave the description and prediction resource empty. Select **Done**.
53
43
54
44
## Create an intent to move employees between cities
55
45
46
+
An intent is used to classify user utterances based on the user's intention, determined from the natural language text.
47
+
48
+
In order to classify an utterance, the intent needs examples of user utterances that should be classified with this intent.
49
+
56
50
1.[!INCLUDE [Start in Build section](../../../includes/cognitive-services-luis-tutorial-build-section.md)]
57
51
58
-
1. Select **Create new intent**.
52
+
1. Select **+ Create**.
59
53
60
54
1. Enter `MoveEmployeeToCity` in the pop-up dialog box then select **Done**.
61
55
62
56
> [!div class="mx-imgBorder"]
63
57
> 
64
58
65
-
1. Add example utterances to the intent.
59
+
1. Add several example utterances to this intent that you expect a user to ask.
66
60
67
61
|Example utterances|
68
62
|--|
@@ -81,18 +75,18 @@ A role should be used when the entity data to extract:
81
75
82
76
## Add prebuilt entity geographyV2
83
77
84
-
The prebuilt entity, geographyV2, extracts location information, including city names. Since the utterances have two city names, relating to each other in context, use roles to extract that context.
78
+
The prebuilt entity, **geographyV2**, extracts location information, including city names. Since the utterances have two city names, relating to each other in context, use roles to extract that context.
85
79
86
80
1. Select **Entities** from the left-side navigation.
87
81
88
-
1. Select **Add prebuilt entity**, then select`geo` in the search bar to filter the prebuilt entities.
82
+
1. Select **+ Add prebuilt entity**, then enter`geo` in the search bar to filter the prebuilt entities.
89
83
90
84
> [!div class="mx-imgBorder"]
91
85
> 
92
86
93
87
1. Select the checkbox and select **Done**.
94
88
1. In the **Entities** list, select the **geographyV2** to open the new entity.
95
-
1. Add two roles, `Origin`, and `Destination`.
89
+
1.To add a role, select Add two roles, `Origin`, and `Destination`.
96
90
97
91
> [!div class="mx-imgBorder"]
98
92
> 
0 commit comments