The skill taxonomy can hallucinate unrelated terms; on this resume it injected American Welding Society Codes even though that text is not in the source.

✗ Failed🧾 artifact-verifiedinput + output shownTest date not recordedAffinda
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: Multi-column sidebar resume — Priya Sharma · pdf · group: resume-parsing
Input — what we sent
parseur-input2-priya-sharma-multicolumnresume-0e443ffc95c3.pdf
Multi-column sidebar resume — Priya Sharma

A two-column sidebar resume for Priya Sharma, used to test whether parsers can preserve reading order and correctly extract content split across columns.

Why this input is hard
  • · multi-column layout handling
  • · sidebar content extraction
  • · reading-order robustness
  • · projects extraction
  • · languages and certifications extraction
Output — unretouched
image
Provenance
Observation
feb0d081-16ca-4ce0-a99c-3f4d39622d58
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: "affinda",
  scenario: "resume-parsing"
})
MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 2 other tools
measured on Noise in output
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com