Triple

T12855902
Position Surface form Disambiguated ID Type / Status
Subject Pittsburgh Steelers–Philadelphia Eagles rivalry E307453 entity
Predicate conferenceMatchup P107232 FINISHED
Object false 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: false | Statement: [Pittsburgh Steelers–Philadelphia Eagles rivalry, conferenceMatchup, false]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conferenceMatchup
Context triple: [Pittsburgh Steelers–Philadelphia Eagles rivalry, conferenceMatchup, false]
  • A. conferenceMatchupType
    Indicates the type or category of matchup between entities within a conference context (e.g., intra-conference vs. inter-conference).
  • B. matchOf
    Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
  • C. finalsMatchup
    Indicates that two competitors or teams are paired to face each other in the final round of a competition or tournament.
  • D. semifinalMatchup
    Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
  • E. refereedMatch
    Indicates that an entity served as the referee or official overseeing and enforcing the rules in a particular match or game.
  • 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_69d7bdf5e7cc8190be357278bc5ba3bb completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9714208f881908f7f8a921362909a completed April 10, 2026, 9:53 p.m.
PD Predicate disambiguation batch_69d96fa3002881908000357b1f95a3ac completed April 10, 2026, 9:46 p.m.
PDg Predicate description generation batch_69d9713e45a88190acd346f066093550 completed April 10, 2026, 9:53 p.m.
Created at: April 9, 2026, 5:37 p.m.