Target word token pattern annotator #135
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
…lized testing of recall booster option
…w of effects in tutorial
…ty (only \d left now) in date regexes
…d small wrapper class for full month tagging where pre match words are added to regex pattern for readability
…rd boundaries and added testing
LydiaMennesHealth
merged commit c4ab115
into
feature_branch/recall_boost
0 of 3 checks passed
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.
Added a annotator called TargetWordTokenPatternAnnotator that inherits from TokenPatternAnnotator and has 2 key differences:
I used this annotator to implement patterns wrt names of people from the social circles of the patient/client. The target words are inidicators like partner/son/daughter etc. While the names can follow the like_name pattern or be a lowercased known first/surname. This means it can catch cases that are not caught by the uppercased known names targeted by first_name_lookup or surname_lookup.