Triple
T23357502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Alberta Athletics and Recreation |
E593088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports and recreation department |
C1499
|
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: sports and recreation department Context triple: [University of Alberta Athletics and Recreation, instanceOf, sports and recreation department]
-
A.
recreation department
chosen
A recreation department is a municipal or organizational unit responsible for planning, organizing, and managing leisure, sports, and community activities and facilities for the public.
-
B.
sports department
A sports department is an organizational unit responsible for planning, managing, and promoting athletic programs, teams, events, and related resources within an institution or company.
-
C.
physical education department
The physical education department is an organizational unit within an educational institution responsible for planning, delivering, and assessing programs that promote students’ physical fitness, motor skills, health knowledge, and lifelong active lifestyles.
-
D.
sports and recreation facility
A sports and recreation facility is a place designed and equipped for individuals or groups to engage in physical activities, sports, exercise, and leisure pursuits.
-
E.
section of multi-sport club
A section of a multi-sport club is a semi-autonomous subdivision dedicated to organizing, managing, and promoting activities, teams, and events for a specific sport within the larger club structure.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:28 p.m.