Triple
T36486379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moon Impact Probe |
E898943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lunar impact probe |
C58651
|
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 impact probe Context triple: [Moon Impact Probe, instanceOf, lunar impact probe]
-
A.
NASA lunar impactor mission
chosen
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.
-
B.
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.
-
C.
lunar seismic experiment
A lunar seismic experiment is a scientific investigation that deploys seismometers on the Moon’s surface to measure and analyze moonquakes and other seismic vibrations, revealing the Moon’s internal structure and geologic activity.
-
D.
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.
-
E.
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.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.