Triple
T24003679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Waterloo varsity games |
E594314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university sports event |
C45395
|
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 event Context triple: [University of Waterloo varsity games, instanceOf, university sports event]
-
A.
university sport event
chosen
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.
university event
A university event is a scheduled gathering or activity organized by or affiliated with a university to engage its community in academic, cultural, social, or professional experiences.
-
D.
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.
-
E.
college football event
A college football event is an organized game or related occasion involving collegiate football teams, typically featuring scheduled competition, spectators, and associated traditions or activities.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:40 p.m.