Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine how best to handle entity confusion results given speech mis-recognitions. #241

Open
rozele opened this issue Dec 21, 2019 · 1 comment

Comments

@rozele
Copy link
Contributor

rozele commented Dec 21, 2019

If I have a test case like:

{
  "text": "contact info for carole",
  "intent": "ContactInfo",
  "entities": [
    {
      "matchText": "carole",
      "entityType": "builtin.personName"
    }
  ]
}

And through speech transcription, we instead get something like:

{
  "text": "contact info for carol",
  "intent": "ContactInfo",
  "entities": [
    {
      "matchText": "carol",
      "entityType": "builtin.personName"
    }
  ]
}

Currently, this is reported as a missing entity.

@rozele
Copy link
Contributor Author

rozele commented Feb 3, 2020

This issue is probably not needed. We can't effectively test ASR -> entity results unless we are testing an end-to-end system and the entities are fully disambiguated.

The correct approach here is to label the ASR output instead of the expected output.

I will file another issue to consider whether we want to remove speech -> LUIS result testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant