Triple
T34962135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna E-3 series |
E1008286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet lunar probe program |
C31914
|
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: Soviet lunar probe program Context triple: [Luna E-3 series, instanceOf, Soviet lunar probe program]
-
A.
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.
-
B.
series of robotic lunar probes
chosen
A series of robotic lunar probes is a coordinated set of unmanned spacecraft missions designed to explore, study, and collect data from the Moon’s surface, subsurface, and environment.
-
C.
lunar exploration program
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.
-
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.
NASA lunar impactor mission
A NASA lunar impactor mission is a spaceflight project in which a spacecraft is deliberately crashed into the Moon’s surface to study its composition, structure, and environment through impact-generated data.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.