Triple

T21178667
Position Surface form Disambiguated ID Type / Status
Subject Arthur Capper E521883 entity
Predicate familyName P18 FINISHED
Object Capper NE NERFINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Capper | Statement: [Arthur Capper, familyName, Capper]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Capper
Context triple: [Arthur Capper, familyName, Capper]
  • A. Capper chosen
    Capper is an English-language surname borne by various notable individuals in politics, sports, and other fields.
  • B. Dunnigan
    Dunnigan is a small unincorporated community in Yolo County, California, known primarily as a rural agricultural area along Interstate 5.
  • C. Dusenberry
    Dusenberry is a surname of English origin borne by various individuals, including American actress Ann Dusenberry.
  • D. Orville Redenbacher
    Orville Redenbacher was an American agriculturalist and entrepreneur best known for creating and marketing a popular brand of gourmet popcorn that bears his name.
  • E. Comer
    Comer is a surname most prominently associated with English actress Jodie Comer, known for her acclaimed role in the television series "Killing Eve."
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69e0b50ef1d48190b063aa342667df22 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7301b41908190bc104aa748a0346d completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 3 p.m.