Triple
T17131671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Launch Services Program |
E415733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | launch services 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: launch services program Context triple: [NASA Launch Services Program, instanceOf, launch services program]
-
A.
launch service provider
A launch service provider is an organization that offers end-to-end services for placing payloads such as satellites or spacecraft into space using launch vehicles and associated ground infrastructure.
-
B.
space launch procurement program
chosen
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.
-
C.
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.
-
D.
NASA program infrastructure
NASA program infrastructure encompasses the organizational structures, facilities, technologies, processes, and support systems that enable the planning, execution, and management of NASA’s missions and research programs.
-
E.
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.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:36 a.m.