Triple
T22365261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Paralympics Track & Field |
E552887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-performance program |
C33576
|
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: high-performance program Context triple: [U.S. Paralympics Track & Field, instanceOf, high-performance program]
-
A.
performance program
chosen
A performance program is a structured plan or set of activities designed to enhance, measure, and showcase the effectiveness, efficiency, or artistic quality of an individual, team, or system over a defined period.
-
B.
high-performance computing system
A high-performance computing system is an integrated collection of powerful processors, high-speed interconnects, and optimized software designed to perform large-scale, complex computations at very high speeds.
-
C.
high-performance computing software
High-performance computing software consists of specialized programs and frameworks designed to efficiently execute large-scale, compute-intensive tasks by exploiting parallelism and advanced hardware architectures such as clusters, supercomputers, and GPUs.
-
D.
programmatic program
A programmatic program is a software application designed to automatically generate, modify, or orchestrate other programs or code through predefined rules, scripts, or algorithms.
-
E.
performance package
A performance package is an optional set of enhancements—such as upgraded powertrain, suspension, brakes, and aerodynamics—designed to improve a vehicle’s speed, handling, and overall driving dynamics.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.