NVIDIA-NeMo / NVIDIA-NeMo/Anonymizer
"X and Y" names are getting tagged as a single entity
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 17
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 11
Description
Priority Level
Medium (Annoying but has workaround)
Describe the bug
I notice the majority of the time in the demo dataset, it tags the kids names - Aria and Leo - as a single first name. Occasionally it correctly identifies them as two separate first names.
In either case, it does the replace part well (i.e. "Aria and Leo" even with tagged as one name still becomes "Claire and Joe").
However, when tagged as one name, it won't properly replace e.g. just "Aria" if she were referenced separately from Leo at a later point. We aren't sure whether this is happening due to GLiNER or the LLM phase of detection. It would be great to add to the base prompt to ensure that values like this get tagged separately.
Steps/Code to reproduce bug
Run the Replace or Your First Anonymization notebook on the first example of the demo dataset about Bobby Watford.
Observe that "Aria and Leo" usually gets tagged as a single entity. Rerun if they happen to get tagged separately.
Expected behavior
"Aria" should get tagged separately from "Leo".
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run the Replace or Your First Anonymization notebook on the first Bobby Watford demo example and reproduce the combined "Aria and Leo" entity. Trace whether the behavior comes from GLiNER or the LLM detection phase, then verify that the two names receive separate tags and can be replaced independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- ai, machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100