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
Is your feature request related to a problem? Please describe.
An additional functionality of tagging terms as 'possible': It's a feature in one of the original negex implementations as well as in pyConTextNLP. Also, some important negation corpora include such annotation (i.e. speculated/possible terms).
Describe the solution you'd like
An example could like this:
doc=nlp("breast cancer may be ruled out")
foreindoc.ents:
print(e.text, e._.negex)
Output:
breastcancerpossible
Obviously, this would require adjusting the return value of e._.negex to be type of i.e. string instead of bool.
This implementation could help when considering the logic behind this feature. In case, anyone wanna run this negex with possible tagging enabled, check this issue here.
The "possible" pre and post triggers ([PREP] and [POSP]) can be also added easily from the the same implementation's negex_triggers.txt file.
Describe alternatives you've considered
None other than using this mentioned negex code separately (combined with spacy, without negspacy).
Additional context
I can refer to the README as well as negex.py files in here. I imagine, step 2. is the only one that would require more work and having good understanding of negspacy.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
An additional functionality of tagging terms as 'possible': It's a feature in one of the original negex implementations as well as in pyConTextNLP. Also, some important negation corpora include such annotation (i.e. speculated/possible terms).
Describe the solution you'd like
An example could like this:
Output:
e._.negex
to be type of i.e. string instead of bool.possible
tagging enabled, check this issue here.negex_triggers.txt
file.Describe alternatives you've considered
None other than using this mentioned negex code separately (combined with spacy, without negspacy).
Additional context
I can refer to the README as well as negex.py files in here. I imagine, step 2. is the only one that would require more work and having good understanding of negspacy.
The text was updated successfully, but these errors were encountered: