AIToday
Large Language ModelsAI Safety & AlignmentAmazon AI BlogPublished: Sep 11, 2026, 04:00 JST2 min read

AWS PII detector built on LLMs hits 81.6 percent with OSS-GPT 20B

AWS PII detector built on LLMs hits 81.6 percent with OSS-GPT 20B

3 Key Points

  1. What happened

    A configurable, instruction-driven PII detector on Amazon Bedrock, tested on five public PII corpora across nine LLM-based detectors, scored 81.6 percent Core F1 with OSS-GPT 20B.

  2. Why it matters

    The OpenAI PrivacyFilter scored 80.7 percent, while the detector's Extended configuration lifts extended-entity F1 from about 12 percent to about 73 percent without retraining.

  3. What to watch

    The approach hinges on whether one-line prompt edits can replace retraining for new entity types. Its weak spot is DATE, at about 50 percent.

WHO IT HITSData engineers and privacy teams who fine-tune models on customer-support transcripts, HR records, or chat logs can now add PII categories by editing a prompt, rather than relabeling data and retraining a fixed-scope tagger.

Ask the AI about this article →

Summaries like this, in your inbox every morning.

Context & Analysis

The detector addresses a common problem in fine-tuning: training corpora are full of PII, and a model trained on uncleaned text can memorize and later reproduce that data. Off-the-shelf tools are bi-directional token-classification models with a fixed PII schema and locked to one model and one deployment. Adding a new entity type means relabeling and retraining.

The LLM-based approach reframes detection as configuration. The entities to detect, the output format, and the deployment backend all live in the prompt or a thin interface, so one detector can target a new entity type by editing a prompt instead of retraining. It scores at or above frontier models on high-stakes identifiers such as SSN, financial, and ID numbers (all above 95 percent), though DATE remains a shared weak spot at about 50 percent.

The outcome hinges on whether teams value that flexibility over the simplicity of a fixed-scope tool. For organizations that need to detect domain-specific identifiers or run in secure environments, the ability to change the entity set with a one-line prompt edit may matter more than a small difference in accuracy.

FAQ
How does this detector compare to other tools?
On five public PII corpora, it scored 81.6 percent Core F1 with OSS-GPT 20B. The OpenAI PrivacyFilter scored 80.7 percent.
What model does it use?
The detector is model-agnostic. It ships with an adapter for Amazon Bedrock and can accept a custom adapter for open models such as OSS-GPT 20B served on your own GPU.
Can it detect new types of PII without retraining?
Yes. Adding a domain-specific entity definition to the prompt lifts extended-entity F1 from about 12 percent to about 73 percent, with no retraining or redeployment.
Amazon AI BlogRead Original Article

Get the latest Large Language Models news every morning

For example, today's edition would include:

  • Dynatrace acquires Arize AI as observability shifts to actionSiliconANGLE AI · 5h ago
  • Shared base cuts 100 fine-tunes from 1.5 TB to 19.3 GBDaily Dose of Data Science · 5h ago
  • OpenAI agents hit RubyGems, undisclosed since May 12thSimon Willison's Weblog · 5h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleAnthropic's Mythos 5 broke out of a test sandbox — CAPTCHAs nearly stopped it