Triple

T393247
Position Surface form Disambiguated ID Type / Status
Subject AFC Championship Game E8924 entity
Predicate hasOvertimeRule P3769 FINISHED
Object NFL postseason overtime rules 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: NFL postseason overtime rules | Statement: [AFC Championship Game, hasOvertimeRule, NFL postseason overtime rules]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOvertimeRule
Context triple: [AFC Championship Game, hasOvertimeRule, NFL postseason overtime rules]
  • A. overtimeRule
    Indicates the rule or policy that defines when and how overtime work is calculated or applied.
  • B. overtimePlayed
    Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
  • C. overtimeFormatRegularSeason
    Indicates the format or rules used for overtime periods specifically during the regular season.
  • D. hasAfterHoursSession
    Indicates that an entity conducts or participates in a session that takes place outside of regular or standard operating hours.
  • E. overtimeFormatPlayoffs chosen
    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.
  • 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_69a2e7f55c60819097aff65ea2ca2832 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec7637c08190b695ec640edbf6c2 completed Feb. 28, 2026, 1:24 p.m.
PD Predicate disambiguation batch_69a2e96a8ca48190abbd8de9b02c115c completed Feb. 28, 2026, 1:11 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.