Triple
T23643697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunokhod programme |
E583969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lunar exploration programme |
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 programme Context triple: [Lunokhod programme, instanceOf, lunar exploration programme]
-
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 sample-return mission
A lunar sample-return mission is a spaceflight endeavor designed to land on the Moon, collect geological material, and transport it safely back to Earth for detailed scientific analysis.
-
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.
space exploration programme
A space exploration programme is an organized, long-term initiative that plans, funds, and conducts missions and research activities to explore outer space and expand scientific and technological knowledge.
-
E.
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.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:48 p.m.