Triple
T9232408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Space Launch |
E221849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space launch procurement program |
C25838
|
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 launch procurement program Context triple: [National Security Space Launch, instanceOf, space launch procurement program]
-
A.
space launch vehicle development program
A space launch vehicle development program is an organized, multi-phase effort to design, test, and qualify rockets and associated systems for reliably delivering payloads from Earth to space.
-
B.
space technology development program
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.
-
C.
spaceflight program phase
A spaceflight program phase is a distinct, time-bounded stage within a space mission or program that groups related objectives, activities, and resources to achieve specific milestones in the overall mission lifecycle.
-
D.
rocket development program
A rocket development program is an organized, multi-phase effort to design, build, test, and refine launch vehicles to meet specific performance, safety, and mission objectives.
-
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. 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:29 p.m.