Modify TimeLogicAdapter to use SpaCy PhraseMatcher instead of NLTK NaiveBayesClassifier #2394
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
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.
Overall the
PhraseMatcherseems to be better suited for the purpose of this logic adapter (matching a set of examples of questions asking what the current time is). Notably this change was brought about by noticing that theTimeLogicAdapterwas being overly confident in its identification of time related statements and was yielding a high number of false-positives.Additionally I'm going to use this pull request to close off a number of old issues related to
nltksince this logic adapter was the last placenltkwas used in ChatterBot.Closes #1746, closes #2138, closes #1953, closes #1857, closes #1856, closes #1813, closes #1800, closes #1720, closes #1618, closes #1678