Triple
T4985910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athlete Performance Awards |
E112001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | athlete funding programme |
C370
|
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 funding programme Context triple: [Athlete Performance Awards, instanceOf, athlete funding programme]
-
A.
competitive funding program
chosen
A competitive funding program is a structured process in which individuals or organizations submit proposals to vie for limited financial resources, with awards granted based on predefined criteria and comparative merit.
-
B.
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.
-
C.
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.
-
D.
multiannual funding programme
A multiannual funding programme is a structured financial initiative that allocates resources over several years to support specified objectives, projects, or policy priorities within a defined framework and timeline.
-
E.
parliamentary funding scheme
A parliamentary funding scheme is a structured system through which a legislature allocates, oversees, and regulates financial resources for political parties, parliamentary activities, or public projects in accordance with legal and budgetary frameworks.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:33 p.m.