Puts four programming languages — Python, JavaScript, SQL, and Bash — into the Languages field even though the resume does not contain a spoken-languages section.

⚠ Struggled🧾 artifact-verifiedinput + output shownTest date not recordedExtracta.ai
What was measured
Noise in output

Does it add incorrect or hallucinated fields?

decisive for this rankingtransformation

Incorrect or hallucinated fields mean the resume parser is not producing reliable structured data, which is central to the job. (3 of 3 judges)

What was given, what came back

Test input: Clean single-column resume — Rugved Nichite · pdf · group: resume-parsing
Input — what we sent
Input file 1 — as supplied
Research media screenshot 202026 05 05 20124028.png
Research media screenshot 202026 05 05 20124028.png
Input file 2 — as supplied
parseur-input1-rugved-nichite-cleanresume-d776e5470f6f.pdf
Clean single-column resume — Rugved Nichite

A professionally structured single-column resume for Rugved Nichite, used as the baseline input for parser accuracy across standard resume fields.

Why this input is hard
  • · baseline field extraction
  • · contact info accuracy
  • · work experience parsing
  • · education and CGPA extraction
  • · skills and certifications extraction
Output — unretouched
image
Provenance
Observation
f89caf00-224f-4aa6-8199-1b2b68ea6d2f
Evidence run
cbbef4db-964c-49fa-a57f-a2977822bdfc
Study
Parse resumes into structured data using an API
Research task
86b9jm30n
Tested at
not recorded
Source
first-party
Evidence state
verified
Proof shown
input + output shown
Cost / latency
not captured
Repeat run
not captured
Tester
not captured

The last three rows are honest blanks, not placeholders — our capture has no field for them yet.

Query this
get_evidence({
  tool: "extracta-labs",
  scenario: "resume-parsing"
})
MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 4 other tools
measured on Noise in output
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com