Triple
T16431834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Sample Return campaign |
E399086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mars exploration program |
C1591
|
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 exploration program Context triple: [Mars Sample Return campaign, instanceOf, Mars exploration program]
-
A.
planetary exploration program
chosen
A planetary exploration program is an organized, long-term initiative that plans, funds, and conducts missions to study other planets and celestial bodies using robotic or crewed spacecraft.
-
B.
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.
-
C.
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.
-
D.
NASA spacecraft program
A NASA spacecraft program is an organized initiative that designs, develops, launches, and operates one or more spacecraft to achieve specific scientific, exploratory, or technological objectives in space.
-
E.
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.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:10 a.m.