Triple

T3339696
Position Surface form Disambiguated ID Type / Status
Subject Denver Broncos–Kansas City Chiefs rivalry E70226 entity
Predicate AFLTeam2RelocationYear P48004 FINISHED
Object 1963 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: 1963 | Statement: [Denver Broncos–Kansas City Chiefs rivalry, AFLTeam2RelocationYear, 1963]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AFLTeam2RelocationYear
Context triple: [Denver Broncos–Kansas City Chiefs rivalry, AFLTeam2RelocationYear, 1963]
  • A. formerTeamRelocation
    Indicates that an entity was previously associated with a team before that team relocated to a different place.
  • B. teamRelocationTo
    Indicates the movement of a team from one location to another as its new home or base of operations.
  • C. teamRelocatedResult
    Indicates that a sports team has changed its home location and specifies the outcome or status resulting from that relocation.
  • D. AFLFranchise
    Indicates that an entity is a franchise (club/team) that competes or has competed in the Australian Football League (AFL).
  • E. teamRelocatedFrom
    Indicates that a team previously based in one location has moved its home base or operations from that original location to a different one.
  • 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_69ad85a405e48190b6e68de7cf9f319e completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb1bf1f648190993ac8e9dda60983 completed March 8, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69ada42c2ba8819091136805ce17b39d completed March 8, 2026, 4:30 p.m.
PDg Predicate description generation batch_69adaa518ac88190b64f949ace018ab7 completed March 8, 2026, 4:56 p.m.
Created at: March 8, 2026, 3:12 p.m.