Triple
T25413464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safe Sport program |
E636765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | athlete protection program |
C50335
|
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: athlete protection program Context triple: [Safe Sport program, instanceOf, athlete protection program]
-
A.
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.
-
B.
Healthy Athletes program component
A Healthy Athletes program component is a specialized module within the broader Healthy Athletes initiative that delivers targeted health screenings, education, and services to athletes in a specific clinical or wellness domain.
-
C.
Paralympic high-performance program
A Paralympic high-performance program is an organized, elite-level system that identifies, develops, and supports athletes with disabilities to achieve optimal performance at national and international Paralympic competitions.
-
D.
sports program
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.
-
E.
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.
- F. None of above. chosen
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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:55 p.m.