NVIDIA-NeMo / NVIDIA-NeMo/Anonymizer

feat(rewrite): Add another LLM detection step to augment entities

Open
#118 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement medium priority
Dominant language
Python
Stars
122
Forks
17
Avg merge
4d 2h
Merged PRs (30d)
11

Description

Priority Level

Medium (Nice to have)

Is your feature request related to a problem?

We'd like the initial entity detection for Rewrite to be very broad. It is only when the Sensitivity Disposition looks at the risk of entities in combination with other entities that the true risk can really be determined. If the entity does not contribute to re-identification risk, then it will choose the disposition of "leave-as-is" and it will not impact the rewrite.

We currently do have the occasional issue of LLM-as-a-Judge for privacy saying too many discriminating attributes are left in the anonymized text. This will help with that.

Describe the solution you'd like

Add one more step in the Rewrite pipeline that uses an LLM to find additional entities. Use domain supplements to guide the prompt.

Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Rewrite pipeline and its existing entity-detection step, then inspect how domain supplements guide prompts. The work is done when an additional LLM-based detection step augments the entities used by Rewrite while allowing Sensitivity Disposition to decide which entities remain unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.