Triple

T2571804
Position Surface form Disambiguated ID Type / Status
Subject Canadian Football League E57679 entity
Predicate introducedOvertimeShootout P39856 FINISHED
Object 2000s LITERAL 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: 2000s | Statement: [Canadian Football League, introducedOvertimeShootout, 2000s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedOvertimeShootout
Context triple: [Canadian Football League, introducedOvertimeShootout, 2000s]
  • A. overtimeFormatPlayoffs
    Indicates that the relationship or action pertains to the specific overtime rules or structure used during playoff games, as distinct from regular-season overtime formats.
  • B. climaxSeriesIntroduced
    Indicates that a particular series is first introduced or begins its climactic phase at a specified point or within a specified context.
  • C. overtimePlayed
    Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
  • D. formerOvertimeRule
    Indicates that a previously applicable overtime rule or regulation no longer applies in the current context.
  • E. penaltyShootoutOccurred
    Indicates that a penalty shootout took place to decide the outcome of a match or contest.
  • F. None of above. chosen

Provenance (4 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_69ab4a51410081908501dcf8bad9adc4 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd383dce881909411a38c6d37bc3a completed March 7, 2026, 7:28 a.m.
PD Predicate disambiguation batch_69abd0ce4dcc8190b17a65abf9bd1bb0 completed March 7, 2026, 7:16 a.m.
PDg Predicate description generation batch_69abd251b48c8190862c7b39ea1bf8ea completed March 7, 2026, 7:22 a.m.
Created at: March 6, 2026, 9:48 p.m.