Triple
T16921021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schiaparelli EDM lander |
E410443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planetary lander technology demonstrator |
C37758
|
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: planetary lander technology demonstrator Context triple: [Schiaparelli EDM lander, instanceOf, planetary lander technology demonstrator]
-
A.
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.
-
B.
rotorcraft lander
A rotorcraft lander is a vertical-takeoff-and-landing spacecraft or planetary probe that uses powered rotors instead of rockets or wings to descend, land, and maneuver near a surface.
-
C.
in-situ resource utilization technology demonstrator
An in-situ resource utilization technology demonstrator is a prototype system designed to test and validate methods for extracting, processing, and using local materials (such as lunar or Martian regolith) to support space missions and reduce dependence on Earth-supplied resources.
-
D.
lunar rover
A lunar rover is a mobile robotic vehicle designed to traverse, explore, and conduct scientific experiments on the surface of the Moon.
-
E.
Mars rover instrument
A Mars rover instrument is a specialized scientific device mounted on a Mars rover that measures, analyzes, or images the Martian environment and geology to support planetary research and exploration objectives.
- F. None of above. chosen
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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.