"X and Y" names are getting tagged as a single entity
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- jupyter-notebook, python
- Domain
- ai, machine-learning
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.
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
- Dominant language
- Python
- Stars
- 129
- Forks
- 21
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from NVIDIA-NeMo/Anonymizer
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NVIDIA-NeMo/Anonymizer#327 ·
Maintainers usually reply within 1 day
-
Replacement-map generation can silently omit a requested entity, causing the rewrite to be marked unavailablePossibly taken @dundysm claimed this 32 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA-NeMo/Anonymizer#278 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NVIDIA-NeMo/Anonymizer#6 · 1 comment ·
Maintainers usually reply within 1 day
-
task
Difficulty 4/5 3-5 days Newbie friendliness 48/100
NVIDIA-NeMo/Anonymizer#323 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
NVIDIA-NeMo/Anonymizer#304 ·
Maintainers usually reply within 1 day
All issues in NVIDIA-NeMo/Anonymizer
Similar issues
-
The changelog workflow excludes otelbot but not dependabot, so every Dependabot pull request fails the changelog checkPossibly taken @ocelotl claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
open-telemetry/opentelemetry-python#5825 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cuga-project/cuga-agent#1020 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
microsoft/playwright#43640 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
stac-utils/stac-fastapi-elasticsearch-opensearch#965 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day