Triple
T11537988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saw Varsity’s Horns Off |
E273597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rivalry tradition |
C2293
|
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: rivalry tradition Context triple: [Saw Varsity’s Horns Off, instanceOf, rivalry tradition]
-
A.
sports rivalry
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.
rivalry trophy
A rivalry trophy is a symbolic award, often passed between competing groups or teams, that represents the ongoing competition and historical significance of their rivalry.
-
C.
university tradition
chosen
A university tradition is a recurring, institution-specific practice or ritual that embodies the shared history, values, and identity of a university community.
-
D.
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.
-
E.
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.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:37 p.m.