Triple
T31975297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Commercial Resupply Services missions |
E816435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cargo spaceflight program |
C29715
|
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: cargo spaceflight program Context triple: [NASA Commercial Resupply Services missions, instanceOf, cargo spaceflight program]
-
A.
spacecraft program
chosen
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.
-
B.
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.
-
C.
human spaceflight program
A human spaceflight program is an organized, long-term governmental or commercial initiative that designs, funds, and operates crewed missions beyond Earth’s atmosphere for exploration, research, and related objectives.
-
D.
NASA spacecraft program
A NASA spacecraft program is an organized initiative that designs, develops, launches, and operates one or more spacecraft to achieve specific scientific, exploratory, or technological objectives in space.
-
E.
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.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:11 a.m.