Triple
T7094549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale University Athletics Director |
E165289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university athletics director role |
C12329
|
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 athletics director role Context triple: [Yale University Athletics Director, instanceOf, university athletics director role]
-
A.
NCAA role
An NCAA role represents a specific position, responsibility, or function held by an individual or entity within the organizational, regulatory, or competitive structure of the National Collegiate Athletic Association.
-
B.
college athletics governing body
A college athletics governing body is an organization that creates, enforces, and oversees rules, eligibility standards, and competition structures for intercollegiate sports programs.
-
C.
sports governance role
chosen
A sports governance role is a position responsible for overseeing the rules, policies, integrity, and strategic direction of sports organizations or competitions.
-
D.
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.
-
E.
college athletic program
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.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:41 p.m.