Triple
T767197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UC Berkeley athletic department |
E16201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college athletic department |
C51
|
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: college athletic department Context triple: [UC Berkeley athletic department, instanceOf, college athletic department]
-
A.
college athletic program
chosen
A college athletic program is an organized set of sports teams, resources, and support services sponsored by a college or university to provide competitive and recreational athletic opportunities for its students.
-
B.
collegiate athletics governance subdivision
A collegiate athletics governance subdivision is an organizational tier within a larger college sports governing body that sets and enforces rules, policies, and competitive structures for a defined group of member institutions.
-
C.
collegiate athletic conference
A collegiate athletic conference is an organized group of colleges and universities that compete against each other in intercollegiate sports under shared rules, governance, and scheduling agreements.
-
D.
college sports venue
A college sports venue is a facility owned or used by a college or university where intercollegiate athletic competitions, practices, and related events are held.
-
E.
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.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.