Triple
T18631992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor lunar lander spacecraft systems |
E455439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lunar lander spacecraft system |
C30132
|
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 lander spacecraft system Context triple: [Surveyor lunar lander spacecraft systems, instanceOf, lunar lander spacecraft system]
-
A.
unmanned lunar lander
chosen
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.
-
B.
asteroid lander
An asteroid lander is a spacecraft designed to descend onto and operate on the surface of an asteroid, conducting scientific measurements, sampling, and in some cases resource prospecting.
-
C.
planetary lander technology demonstrator
A planetary lander technology demonstrator is a prototype spacecraft designed to test and validate key landing systems, instruments, and operations for future missions to planetary surfaces.
-
D.
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.
-
E.
lunar rover
A lunar rover is a mobile robotic vehicle designed to traverse, explore, and conduct scientific experiments on the surface of the Moon.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.