Triple
T11772272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonsei–Korea sports rivalry |
E279928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university 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: university rivalry Context triple: [Yonsei–Korea sports rivalry, instanceOf, university 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.
university sports competitions
University sports competitions are organized athletic events in which teams or individuals representing higher education institutions compete under standardized rules to promote physical excellence, school spirit, and intercollegiate rivalry.
-
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.
sports college
A sports college is an educational institution that combines academic programs with specialized training and development in various athletic disciplines to prepare students for careers in sports and related fields.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.