Triple
T24704068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keri Alexander Luchowski |
E611838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college athletics commissioner |
C31916
|
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 athletics commissioner Context triple: [Keri Alexander Luchowski, instanceOf, college athletics commissioner]
-
A.
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.
-
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 commissioner
A sports commissioner is the chief executive and governing authority of a professional sports league, responsible for overseeing operations, enforcing rules, negotiating major agreements, and safeguarding the integrity and commercial success of the league.
-
D.
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.
-
E.
league commissioner position
chosen
A league commissioner position is a leadership role responsible for overseeing the operations, governance, and strategic direction of a sports or competitive league, ensuring rules compliance, competitive balance, and long-term stability.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 3:23 a.m.