Triple
T12681408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Lunar Payload Services |
E302955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial lunar delivery program |
C1385
|
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: commercial lunar delivery program Context triple: [Commercial Lunar Payload Services, instanceOf, commercial lunar delivery program]
-
A.
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.
-
B.
lunar exploration program
chosen
A lunar exploration program is an organized, long-term initiative that plans, funds, and conducts missions to study, visit, and potentially utilize the Moon’s environment and resources.
-
C.
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.
-
D.
space mission rideshare platform
A space mission rideshare platform is a digital marketplace that connects satellite operators and payload customers with available launch capacity on rockets, enabling shared missions, cost savings, and streamlined logistics for accessing space.
-
E.
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.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:21 p.m.