Reducing Biases in Record Matching Through Scores Calibration
This paper introduces a threshold-independent metric for quantifying score bias in record matching and proposes two model-agnostic post-processing methods, Calib and C-Calib, that effectively mitigate demographic parity and equalized odds disparities by aligning group-wise score distributions via optimal transport without retraining the underlying models.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are a hiring manager at a massive company. You have thousands of resumes (records) and you need to find the ones that belong to the same person (matching). To do this, you use a smart computer program that gives every pair of resumes a "Match Score" between 0 and 100.
- 90-100: "These are definitely the same person!"
- 0-10: "These are totally different people."
- 40-60: "I'm not sure, maybe?"
Usually, the manager sets a cutoff line (a threshold). If the score is above 50, they say "Match!" If it's below, they say "No match."
The Problem: The "Hidden" Unfairness
The paper argues that we've been looking at fairness the wrong way. We've been checking if the computer makes the same number of "Match" decisions for men and women at that specific 50-point cutoff.
But the authors say: "That's like judging a chef only by whether they salt the soup at the exact moment you taste it, ignoring the fact that they might have added too much salt to the pot for the whole week."
The computer might be giving scores that are subtly biased.
- For Group A (e.g., men), a "maybe" match might get a score of 55.
- For Group B (e.g., women), the exact same "maybe" match might get a score of 45.
If your cutoff is 50, Group A gets hired, and Group B gets rejected. Even if you change the cutoff to 40 or 60, the gap remains. The scores themselves are unfair, even if the final "Yes/No" decision looks okay at one specific moment.
The Solution: The "Score Calibrator"
The authors propose a way to fix these scores after the computer has already done its work, without needing to retrain the computer or know the "true" answers (which are often hidden). They call this Calibration.
Think of it like a Sound Engineer mixing a song. The original recording (the scores) has the bass (Group A) too loud and the treble (Group B) too quiet. The engineer doesn't rewrite the song; they just use a mixer to balance the volumes so both groups sound equally clear.
They offer two tools for this:
1. Calib: The "Volume Balancer" (For General Fairness)
This tool fixes Demographic Parity. It asks: "Do both groups get the same range of scores?"
- How it works: Imagine you have a bag of red marbles (Group A) and a bag of blue marbles (Group B). The red marbles are mostly heavy (high scores), and the blue ones are mostly light (low scores).
- The tool creates a "Target Bag" (a mathematical average called a Wasserstein Barycenter) that represents a perfect, balanced mix of weights.
- It then gently nudges the red marbles down and the blue marbles up until both bags have the exact same distribution of weights.
- The Result: Now, a "heavy" score for a red marble means the same thing as a "heavy" score for a blue marble. The playing field is level.
2. C-Calib: The "Context-Aware Balancer" (For Specific Fairness)
Sometimes, you need to be fair within specific situations. This is Equal Opportunity.
- Example: "If a person is actually qualified (a true match), they should get a high score, regardless of their group."
- The Problem: The computer doesn't know who is "actually qualified" (the true label) when it's just calibrating.
- The Fix: C-Calib is a bit like a detective. It guesses who is qualified based on the scores (e.g., "If the score is high, I'll guess they are qualified").
- It then splits the marbles into two piles: "Likely Qualified" and "Likely Not Qualified."
- It balances the scores inside each pile separately. It ensures that among the "Likely Qualified" group, men and women get the same high scores. It does the same for the "Likely Not Qualified" group.
Why This Matters
The paper tested this on real-world data (like matching academic papers or product listings). They found that:
- Hidden Bias is Real: Even the smartest, most modern AI models give unfair scores to different groups, even if they look fair at a single cutoff point.
- The Fix Works: Using their "Calibrator" tools, they could fix the unfairness significantly.
- No Harm Done: Crucially, fixing the scores didn't make the computer worse at its job. The accuracy stayed almost the same. It's like tuning a guitar: you make it sound fairer without changing the song.
The Big Takeaway
We often judge AI by a simple "Pass/Fail" test. But in the real world, AI gives us confidence scores (like a weather forecast saying "70% chance of rain"). If that forecast is biased against certain neighborhoods, the "Pass/Fail" test might miss it.
This paper gives us a new way to tune the forecast itself, ensuring that the "70%" means the same thing for everyone, no matter who they are. It's about making the numbers fair, not just the final decision.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.