-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
NER: all confidences per Token with DIETClassifier #7299
Comments
Exalate commented: sara-tagger commented: Thanks for submitting this feature request |
Exalate commented: Novaal commented: It seems to be, that rasa/rasa/nlu/classifiers/diet_classifier.py Line 859 in 9690842
|
Exalate commented: stale[bot] commented: This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
➤ Maxime Verger commented: 💡 Heads up! We're moving issues to Jira: https://rasa-open-source.atlassian.net/browse/OSS. From now on, this Jira board is the place where you can browse (without an account) and create issues (you'll need a free Jira account for that). This GitHub issue has already been migrated to Jira and will be closed on January 9th, 2023. Do not forget to subscribe to the corresponding Jira issue! ➡️ More information in the forum: https://forum.rasa.com/t/migration-of-rasa-oss-issues-to-jira/56569. |
Description of Problem: Thanks for introducing the confidences for NER with #6038. Currently only the labels for the best matching entity is given. I would like to have an option to get all confidences including the confidences for labels with
NO_ENTITY_TAG
on a per token basis. This would allow me for example to choose the second best entity for specific tokens.Overview of the Solution:
Change _predict_entities() to return a list of confidences on a per Token basis.
Examples (if relevant):
rasa/rasa/nlu/extractors/extractor.py
Line 131 in 2e7f49f
It could be an similar aproach like in _predict_label()
The text was updated successfully, but these errors were encountered: