Triple
T22134444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Launch Alliance Vulcan program |
E546989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | launch vehicle development program |
C12851
|
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: launch vehicle development program Context triple: [United Launch Alliance Vulcan program, instanceOf, launch vehicle development program]
-
A.
space launch vehicle development program
chosen
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.
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.
-
C.
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.
-
D.
spacecraft program
A spacecraft program is an organized, long-term initiative that plans, develops, launches, and operates one or more spacecraft to achieve specific scientific, commercial, or exploratory objectives.
-
E.
space launch procurement program
A space launch procurement program is an organized framework through which a government or commercial entity acquires launch services, vehicles, and related support to place payloads into space under defined technical, schedule, and cost requirements.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:32 p.m.