Triple
T12681407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Lunar Payload Services |
E302955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lunar exploration initiative |
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: lunar exploration initiative Context triple: [Commercial Lunar Payload Services, instanceOf, lunar exploration initiative]
-
A.
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.
-
B.
lunar landing mission
A lunar landing mission is a coordinated spaceflight operation designed to transport a spacecraft from Earth to the Moon, achieve a controlled descent and landing on the lunar surface, conduct scientific or exploratory activities, and safely return data and/or crew.
-
C.
lunar orbiter mission
A lunar orbiter mission is a spaceflight operation in which a spacecraft is placed into orbit around the Moon to conduct sustained observations, measurements, and communications for scientific, exploration, or operational objectives.
-
D.
planetary exploration program
A planetary exploration program is an organized, long-term initiative that plans, funds, and conducts missions to study other planets and celestial bodies using robotic or crewed spacecraft.
-
E.
unmanned lunar lander
An unmanned lunar lander is a robotic spacecraft designed to descend from lunar orbit and safely touch down on the Moon’s surface to conduct scientific experiments, deploy instruments, or support future missions without a human crew onboard.
- 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.