Triple
T28547496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Napolillo |
E722484
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegiate athletics administrator |
C32143
|
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: collegiate athletics administrator Context triple: [Steve Napolillo, instanceOf, collegiate athletics administrator]
-
A.
college athletic director
chosen
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.
-
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.
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.
-
D.
academic administrator
An academic administrator is a professional responsible for planning, organizing, and overseeing the non-teaching operations and policies of educational institutions to support their academic mission.
-
E.
collegiate athletes
Collegiate athletes are students enrolled in higher education institutions who participate in organized, competitive sports sanctioned by collegiate athletic associations while balancing academic and athletic commitments.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:40 a.m.