huggingface / huggingface/neuralcoref
Allowing for custom blacklist
- Dominant language
- C
- Stars
- 2.9k
- Forks
- 467
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Thanks a lot for this amazing extension to spaCy. I have used it in a project and it was very helpful.
I was wondering if it is possible to add a feature where one can pass a custom list for the blacklist parameter.
For instance:
If blacklist is enabled
```
nlp("I really liked that ice cream. My dog did not.")._.coref_resolved
```
returns "I really liked that ice cream. My dog did not." unchanged.
However, 'we', 'out', 'us' are not in the blacklist, so,
```
nlp("We really liked that ice cream. Our dog did not.")._.coref_resolved
```
returns "We really liked that ice cream. We dog did not."
It would be very helpful if it was possible to customise the blacklist.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the blacklist parameter and the coref_resolved extension described in the examples. Check how blacklist values are configured and applied, then define the custom-list interface and verify that supplied terms remain unchanged while existing blacklist behavior is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100