Update 'convert_predictions_into_entities' #6191
Merged
Conversation
This file contains 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
tabergma
force-pushed
the
entity-creation
branch
from
aaf097a to
d887e40
Compare
ricwo
reviewed
Jul 14, 2020
ricwo
approved these changes
Jul 14, 2020
tabergma
added a commit
that referenced
this pull request
Aug 21, 2020
This was referenced Sep 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes:
If two entities are separated by a comma, they are currently detected as one entity. Example:
please add buffalo, ranch, mustard, barbeque saucesresults in{'entity': 'sauces', 'start': 11, 'end': 43, 'value': 'buffalo, ranch, mustard, barbeque', 'extractor': 'DIETClassifier'}This PR fixes this. Entities separated by a comma will be listed as individual entities.
Related to forum post
Status (please check what you already did):
black(please check Readme for instructions)