Triple
T26762334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varsity Athletics Match |
E674838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university sports rivalry event |
C46781
|
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 sports rivalry event Context triple: [Varsity Athletics Match, instanceOf, university sports rivalry event]
-
A.
university sport event
A university sport event is an organized athletic competition or activity hosted by a higher education institution, involving student participants and often spectators, to promote physical fitness, school spirit, and community engagement.
-
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.
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.
-
D.
NCAA rivalry
chosen
An NCAA rivalry is a recurring, highly competitive athletic contest between two college or university programs, often fueled by historical, geographic, or cultural tensions and traditions.
-
E.
intercollegiate competition
An intercollegiate competition is an organized contest in which teams or individuals representing different colleges or universities compete against one another under agreed-upon rules.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:58 a.m.