Triple

T33246240
Position Surface form Disambiguated ID Type / Status
Subject 1983 AFC Championship Game E851107 entity
Predicate isRematchOfRegularSeasonGame P63572 FINISHED
Object true 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: true | Statement: [1983 AFC Championship Game, isRematchOfRegularSeasonGame, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRematchOfRegularSeasonGame
Context triple: [1983 AFC Championship Game, isRematchOfRegularSeasonGame, true]
  • A. isRematchOfFinal
    Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
  • B. wasRematchOf chosen
    Indicates that an event or contest is a subsequent encounter between the same parties, held as a repeat of a previous matchup.
  • C. isPostseasonGame
    Indicates that the game takes place during a postseason or playoff phase rather than the regular season.
  • D. isConferenceGame
    Indicates that a particular game is played between teams within the same athletic conference and counts toward conference standings.
  • E. isMidseasonExhibition
    Indicates that an event is a special exhibition or showcase taking place in the middle of a regular season or series.
  • F. None of above.

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_69f34962386c81909ddc3bf9e18ddeb8 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6daf3963081909fc96cbd1642cd21 completed May 3, 2026, 5:19 a.m.
PD Predicate disambiguation batch_69f6d82fef788190b9ad19a36c0312dc completed May 3, 2026, 5:08 a.m.
Created at: May 1, 2026, 1:31 a.m.