Adds support for entity hierarchies in compare #346
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change allows users to declaratively specify hierarchical entities in their expected utterance results. For example, a user may declare the following:
```json
{
"text": "Order a pepperoni pizza",
"intent": "OrderFood",
"entities": {
"entity": "FoodItem",
"startPos": 8,
"endPos": 22,
"children": [
{
"entity": "Topping",
"startPos": 8,
"endPos": 16
},
{
"entity": "FoodType",
"startPos": 18,
"endPos": 22
}
]
}
}
```
This would result in 3 test cases, one for the parent entity (the "FoodItem" entity), and two additional test cases for each of the two nested entities ("FoodItem::Topping" and "FoodItem::FoodType").
Child entity type names are prefixed by their parent entity type names in the format `parentType::childType`. As such, the recursive entity parsing for the LUIS V3 provider has been updated to use this convention.
Fixes microsoft#335
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change allows users to declaratively specify hierarchical entities in their expected utterance results. For example, a user may declare the following:
{ "text": "Order a pepperoni pizza", "intent": "OrderFood", "entities": { "entity": "FoodItem", "startPos": 8, "endPos": 22, "children": [ { "entity": "Topping", "startPos": 8, "endPos": 16 }, { "entity": "FoodType", "startPos": 18, "endPos": 22 } ] } }This would result in 3 test cases, one for the parent entity (the "FoodItem" entity), and two additional test cases for each of the two nested entities ("FoodItem::Topping" and "FoodItem::FoodType").
Child entity type names are prefixed by their parent entity type names in the format
parentType::childType. As such, the recursive entity parsing for the LUIS V3 provider has been updated to use this convention.Fixes #335