Triple
T15271219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game Changing Development Program |
E365024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space technology maturation initiative |
C14138
|
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: space technology maturation initiative Context triple: [Game Changing Development Program, instanceOf, space technology maturation initiative]
-
A.
space technology development program
chosen
A space technology development program is an organized initiative that researches, designs, tests, and matures advanced space-related technologies to enable or enhance future space missions and capabilities.
-
B.
space technology
Space technology encompasses the tools, systems, and methods used to explore, utilize, and operate in outer space, including spacecraft, satellites, launch vehicles, and supporting ground infrastructure.
-
C.
space technology
Space technology encompasses the tools, systems, and methods developed to explore, utilize, and operate in outer space, including spacecraft, satellites, launch vehicles, and supporting ground infrastructure.
-
D.
space infrastructure project
A space infrastructure project is a large-scale, coordinated initiative to design, build, and operate physical and digital systems that enable sustained activities and services in space, such as communication, transportation, energy, and research.
-
E.
space access mission area
The space access mission area encompasses the systems, operations, and infrastructure required to reliably and affordably deliver payloads and humans from Earth to space and between orbital or celestial destinations.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:14 a.m.