Triple
T35916889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTSU Cheerleading |
E1038773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | athletics spirit program |
C7949
|
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: athletics spirit program Context triple: [MTSU Cheerleading, instanceOf, athletics spirit program]
-
A.
track and field program
A track and field program is an organized system of training, competition, and athlete development that coordinates events, coaching, facilities, and resources for participants in running, jumping, and throwing disciplines.
-
B.
sports program
chosen
A sports program is an organized set of athletic activities, training sessions, and events designed to develop participants’ physical skills, teamwork, and competitive performance within a structured schedule.
-
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.
sports medicine program
A sports medicine program is a coordinated set of services and educational activities designed to prevent, diagnose, treat, and rehabilitate sports- and exercise-related injuries while optimizing athletes’ health and performance.
-
E.
athletic festival
An athletic festival is a planned event featuring a variety of sports competitions, physical activities, and related celebrations that bring participants and spectators together in a communal setting.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.