Triple
T26762200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford University Korfball Club |
E674834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university korfball club |
C52016
|
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 korfball club Context triple: [Oxford University Korfball Club, instanceOf, university korfball club]
-
A.
university football club
A university football club is a student-organized sports group that represents the institution in football competitions while providing members with training, teamwork, and social engagement opportunities.
-
B.
university basketball team
A university basketball team is an organized group of student-athletes representing their institution in competitive collegiate basketball, balancing academic responsibilities with training, teamwork, and intercollegiate games.
-
C.
university basketball team
A university basketball team is an organized group of student-athletes representing their institution in competitive intercollegiate basketball games and tournaments.
-
D.
university football team
A university football team is an organized group of student-athletes representing their institution in competitive American football, typically governed by collegiate athletic associations and supported by the campus community.
-
E.
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.
- F. None of above. chosen
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.