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
We think that it may not make lots of sense to test for entities with ASR.
how do we handle entities that are likely misspelled by ASR?
The batch testing has a labeled set of utterances to compare with, and both the testing and training need to be of the same data that is used. In turn if this is a pipeline that follows from ASR as the only source then the utterances should be those after ASR, and not textual that are perfect. In turn this wouldn’t be an issue. It is more of an issue with the model being trained with generated data that doesn’t have speech errors, and using ASR ahead. Using the ASR output would be measuring something else other than performance.
The text was updated successfully, but these errors were encountered:
We think that it may not make lots of sense to test for entities with ASR.
The text was updated successfully, but these errors were encountered: