Triple
T26856236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford University Ultimate Frisbee Club |
E676202
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university ultimate frisbee club |
C46058
|
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 ultimate frisbee club Context triple: [Oxford University Ultimate Frisbee Club, instanceOf, university ultimate frisbee club]
-
A.
ultimate frisbee team
chosen
An ultimate frisbee team is a coordinated group of players who work together to advance a flying disc up the field and score points by catching it in the opposing end zone while adhering to the sport’s principles of self-officiation and fair play.
-
B.
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.
-
C.
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.
-
D.
undergraduate student organization
An undergraduate student organization is a formally recognized group of college students who collaborate around shared interests, goals, or identities to provide activities, support, and community within the university.
-
E.
university baseball team
A university baseball team is an organized group of student-athletes representing their institution in collegiate baseball competitions, practices, and related 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:21 a.m.