Triple
T28885413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pride |
E732545
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NCAA athletic program identity |
C37461
|
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: NCAA athletic program identity Context triple: [Pride, instanceOf, NCAA athletic program identity]
-
A.
NCAA athletics brand
chosen
An NCAA athletics brand is the cohesive identity—encompassing visual design, messaging, traditions, and values—that represents a college or university’s sports programs across teams, media, and fan experiences.
-
B.
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.
-
C.
high school athletic program
A high school athletic program is an organized set of school-sponsored sports teams, activities, and support services designed to promote student physical fitness, skill development, teamwork, and school spirit through structured competition and training.
-
D.
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.
-
E.
University of Illinois athletic programs
The University of Illinois athletic programs encompass the varsity, club, and intramural sports teams and activities representing the university in intercollegiate competition, student recreation, and community engagement.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:49 a.m.