Triple
T18461158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixth Street Rivalry |
E451037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intercollegiate 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: intercollegiate rivalry Context triple: [Sixth Street Rivalry, instanceOf, intercollegiate 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.
regional rivalry
Regional rivalry is a competitive and often tense relationship between neighboring areas or countries, driven by historical, cultural, economic, or political differences as they vie for influence, resources, or prestige.
-
C.
college basketball rivalry
A college basketball rivalry is a recurring, highly competitive series of games between two collegiate teams characterized by historical significance, regional or conference proximity, and intense fan and media interest.
-
D.
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.
-
E.
intercollegiate athletic events
Intercollegiate athletic events are organized sports competitions in which teams or individuals representing different colleges or universities compete under established rules and governing bodies.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:33 a.m.