Triple

T22428597
Position Surface form Disambiguated ID Type / Status
Subject Thurman Arnold E554436 entity
Predicate givenName P17 FINISHED
Object Thurman 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: Thurman | Statement: [Thurman Arnold, givenName, Thurman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thurman
Context triple: [Thurman Arnold, givenName, Thurman]
  • A. Thurman chosen
    Thurman is the given name of Thurman Thomas, a Hall of Fame former NFL running back best known for his career with the Buffalo Bills.
  • B. Erdman
    Erdman is a masculine given name most notably borne by Disney story artist and screenwriter Erdman Penner.
  • C. Furthman
    Furthman is a surname most notably associated with American screenwriter Jules Furthman, known for his work on classic Hollywood films.
  • D. Trueman
    Trueman is a surname most famously associated with Fred Trueman, one of England’s greatest fast bowlers in cricket history.
  • E. Lamon
    Lamon is an archaeological site notable for inscriptions in the ancient Venetic language.
  • 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_69e11e4f2d0c819091aa3558ea2ee630 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15a2f054c819093fbe173c8a4a544 completed April 29, 2026, 1:09 a.m.
Created at: April 16, 2026, 8:47 p.m.