Triple
T14824350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Origin |
E348532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sporting rivalry |
C778
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: sporting rivalry Context triple: [Origin, instanceOf, sporting rivalry]
-
A.
sports rivalry
chosen
A sports rivalry is a competitive relationship between teams, athletes, or fan bases characterized by repeated contests, heightened emotions, and historical or cultural significance that intensifies their matchups.
-
B.
rugby union rivalry
A rugby union rivalry is a recurring, often historically rooted competitive relationship between two rugby union teams or nations, characterized by intense matches, strong fan engagement, and cultural or regional significance beyond ordinary fixtures.
-
C.
ice hockey rivalry
An ice hockey rivalry is a competitive and often intense ongoing relationship between two ice hockey teams, fueled by repeated matchups, historical context, geographic proximity, or cultural factors that heighten fan and player emotions.
-
D.
sports competition
A sports competition is an organized event in which individuals or teams engage in athletic contests under defined rules to determine a winner or ranking.
-
E.
soccer rivalry trophy
A soccer rivalry trophy is a symbolic award contested between two or more soccer teams, typically given to the winner of their recurring matches to commemorate and intensify their competitive rivalry.
- F. None of above.
Provenance (1 batch)
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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:51 a.m.