Ground truth errors bias weaker scores across all models

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
python

Research direction

Start by locating the frozen test corpus and the evaluation or judging entry points, then inspect examples 1c73243f-9814-4252-a6b5-af03062f39c4 and f69fb188-7bbc-4b17-80b0-177dd2b6bf18. Compare their samples and ground truths with the reported outputs; completion should include a documented review method and an evidence-based ground-truth error rate.

Written by the indexing model from the issue text.

Description

While using this to enhance a mutimodal pipeline w/ Qwen3.8-27B, we've noticed that while the test corpus remains reproducible for benchmarking due to the frozen state of the test examples, it does not make it reliable. It should probably not be used as unreviewed training data as far as an actual pass/fail for vision models accuracy.

Image Image

A simple spot-review of examples which our own harness plus additional context could not pass, on review, shows the defect is often with the sample and/or the ground truth being inaccurate.

Examples included:
1c73243f-9814-4252-a6b5-af03062f39c4
f69fb188-7bbc-4b17-80b0-177dd2b6bf18

First, and only two, that I've checked out of thousands, but you can see the problem with this method. This paints frontier models and the other models tested in a potentially weaker light as to their true abilities.

From the paper:
"The majority of reviewers agreed with the automated judge 97.1% of the time. All three reviewers unanimously considered the judge wrong in 5/477 = 1.0% of cases"

More helpful study information would be the expected error rate of the ground truths. I could not find that metric or that any review was done.

Dominant language
Python
Stars
11
Forks
1
PR merge metrics
No merged PRs in 30d

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.

More from Tencent/DiffSpot

All issues in Tencent/DiffSpot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.