Triple

T12486297
Position Surface form Disambiguated ID Type / Status
Subject Charles Tillman E298440 entity
Predicate familyName P18 FINISHED
Object Tillman E550469 NE FINISHED

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: Tillman | Statement: [Charles Tillman, familyName, Tillman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tillman
Context triple: [Charles Tillman, familyName, Tillman]
  • A. Tillman chosen
    Tillman is a surname most famously associated with Pat Tillman, the former NFL player who left his football career to enlist in the U.S. Army and was killed in Afghanistan.
  • B. Talbott
    Talbott is an unincorporated community in Hamblen County, Tennessee, known primarily as a residential area near the city of Morristown.
  • C. Talmadge
    Talmadge is an American surname notably associated with several political and public figures, including members of the Talmadge family in Georgia.
  • D. Heflin
    Heflin is a small city in eastern Alabama that serves as the administrative and commercial hub of Cleburne County.
  • E. Gilchrist
    Gilchrist is a surname of Scottish origin borne by various notable individuals in fields such as acting, sports, and public service.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6ada377208190a36011199a4d8558 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94de077bc81908b5ff057a1bf2b4f completed April 10, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f63f2b5ed481909ead4f5b96d44064 completed May 2, 2026, 6:15 p.m.
Created at: April 8, 2026, 9:56 p.m.