Triple

T4300480
Position Surface form Disambiguated ID Type / Status
Subject Snodgrass E99821 entity
Predicate hasNotableBearer P458 FINISHED
Object William Snodgrass E429269 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: William Snodgrass | Statement: [Snodgrass, hasNotableBearer, William Snodgrass]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: William Snodgrass
Context triple: [Snodgrass, hasNotableBearer, William Snodgrass]
  • A. Charles Snodgrass
    Charles Snodgrass is a person notable enough to be recognized as a primary bearer of the surname Snodgrass.
  • B. William David Snodgrass chosen
    William David Snodgrass was an American poet known for his confessional style and for winning the Pulitzer Prize for Poetry for his debut collection "Heart's Needle."
  • C. Fred Snodgrass
    Fred Snodgrass was an American Major League Baseball outfielder best remembered for his infamous dropped fly ball in the 1912 World Series.
  • D. John Snodgrass
    John Snodgrass is a notable individual distinguished enough to be specifically recognized as a bearer of the Snodgrass surname.
  • E. David Snodgrass
    David Snodgrass is a person notable enough to be specifically referenced as a bearer of the surname Snodgrass.
  • 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_69b345528ebc8190b5abc7e95094792d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3509e8cb481909ccca7992aac31a3 completed March 12, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b627cfba848190a56a25c6d7d750c7 completed March 15, 2026, 3:30 a.m.
Created at: March 12, 2026, 11:08 p.m.