Triple

T14861738
Position Surface form Disambiguated ID Type / Status
Subject John Scott E349508 entity
Predicate hasGivenName P17 FINISHED
Object John E55602 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: John | Statement: [John Scott, hasGivenName, John]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: John
Context triple: [John Scott, hasGivenName, John]
  • A. John chosen
    John is a masculine given name of Hebrew origin, widely used in English-speaking countries and borne by numerous historical and contemporary figures.
  • B. John
    John is the nickname of John Riggins, a former American football running back best known for his Hall of Fame career with the Washington Redskins in the NFL.
  • C. John
    John is the given name of John Reith, the influential first Director-General of the BBC who shaped early public service broadcasting in the United Kingdom.
  • D. John
    John is the given first name of American character actor and comedian Rags Ragland.
  • E. John
    John is the first name of the fictional character John Connor, the prophesied leader of the human resistance in the Terminator franchise.
  • 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_69d822ed7e1881909b90fca143ad7e34 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded573cba881908d6d9ac570a64e5f completed April 15, 2026, 12:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe72a87dd88190b0f0c3b9b625a7e6 completed May 8, 2026, 11:32 p.m.
Created at: April 10, 2026, 1:54 a.m.