Triple
T16921263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martian Moons eXploration mission |
E410448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mars system mission |
C37760
|
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: Mars system mission Context triple: [Martian Moons eXploration mission, instanceOf, Mars system mission]
-
A.
Mars rover mission
A Mars rover mission is a space exploration endeavor that lands a robotic vehicle on Mars to traverse the surface, conduct scientific experiments, and transmit data back to Earth.
-
B.
Mars mission engineering activity
Mars mission engineering activity encompasses the planning, design, testing, and integration of systems and technologies required to safely transport, land, and support missions on the Martian surface and in its orbit.
-
C.
Mars orbiter payload
A Mars orbiter payload is the collection of scientific instruments, sensors, and supporting hardware carried by a spacecraft in Mars orbit to observe, measure, and transmit data about the planet’s atmosphere, surface, interior, and space environment.
-
D.
planetary science mission element
A planetary science mission element is a distinct component or subsystem of a space mission—such as an instrument, spacecraft module, or operational capability—designed to enable the collection, transmission, or analysis of scientific data about planets and other solar system bodies.
-
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.