Triple

T21136157
Position Surface form Disambiguated ID Type / Status
Subject Kansas–Missouri rivalry E520821 entity
Predicate alsoKnownAs P39 FINISHED
Object Border Showdown 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: Border Showdown | Statement: [Kansas–Missouri rivalry, alsoKnownAs, Border Showdown]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Border Showdown
Context triple: [Kansas–Missouri rivalry, alsoKnownAs, Border Showdown]
  • A. Border Showdown chosen
    Border Showdown is the intense college football rivalry game between the University of Missouri Tigers and the University of Kansas Jayhawks.
  • B. Showdown
    Showdown is the fiercely contested Australian Football League derby between the Port Adelaide Football Club and the Adelaide Crows.
  • C. Showdown
    "Showdown" is a 1973 rock song by Electric Light Orchestra, known for its lush orchestration and fusion of rock and classical influences.
  • D. Showdown
    "Showdown" is a song featured on the album *In the Zone* by American pop singer Britney Spears.
  • E. Showdown
    Showdown is a climactic segment or episode within "The E.N.D." that serves as a decisive confrontation or resolution point in the work’s narrative.
  • 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_69e0b50b53048190ae34e8abbe3c5ada completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7235aae588190bf9f7b40553bfa0e completed April 21, 2026, 7:12 a.m.
Created at: April 16, 2026, 2:57 p.m.