NVIDIA-NeMo / NVIDIA-NeMo/Curator

Classifier-Calibration Audit (Data-Quality Illusion)

Open
#1,750 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
1.8k
Forks
327
Avg merge
4d 5h
Merged PRs (30d)
30

Description

What:
Add a diagnostic stage that audits whether a trained quality classifier (e.g., FineWeb-Edu-style fastText/LLM classifier) is capturing genuine quality signal or distributional artifacts. Tests: (1) whether filtered data improves language modeling on the reference set, (2) whether classifier scores correlate with held-out human quality judgments, (3) whether the classifier implicitly re-filters the reference dataset itself.

Why:
arXiv:2510.00866 proves that Classifier-based Quality Filtering improves downstream task performance but does not improve language modeling on the high-quality reference set. The classifier exploits distributional artifacts, not genuine quality. Without this audit, practitioners trust classifiers that may be overfitting to distribution shift rather than quality — leading to compounding errors across pipelines.

Definition of Done:

  • ClassifierCalibrationAudit under nemo_curator/audit/
  • Test 1 — Reference LM check: trains a 125M proxy on filtered data vs. unfiltered, computes perplexity on reference corpus (not benchmark); flags if
    filtered model is worse
  • Test 2 — Human correlation: accepts optional human-annotated quality sample; reports Spearman ρ between classifier score and human rating
  • Test 3 — Reference contamination check: applies classifier to the reference dataset itself; reports what fraction the classifier would remove (should be
    near 0% for a calibrated classifier)
  • Outputs an audit report JSON with pass/warn/fail per test
  • Integration test: a deliberately miscalibrated classifier (trained on distribution-shifted data) should trigger warnings
  • Tutorial: auditing a custom-trained classifier before deploying to production pipeline

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 surveying the new nemo_curator/audit/ area and the classifier and reference-corpus entry points involved in the Definition of Done. Map the three requested checks, the pass/warn/fail JSON report, the deliberately miscalibrated integration case, and the custom-classifier tutorial before implementation; done means all three diagnostics and their integration coverage are present.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data, machine-learning, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.