Triple
T27634760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple University athletics |
E696439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intercollegiate athletics department |
C33905
|
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: intercollegiate athletics department Context triple: [Temple University athletics, instanceOf, intercollegiate athletics department]
-
A.
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.
-
B.
college athletic director
A college athletic director is the senior administrator responsible for overseeing all aspects of a college or university’s athletic programs, including budgeting, compliance, staffing, facilities, and strategic planning.
-
C.
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.
-
D.
sports department
chosen
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.
-
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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:23 p.m.