Triple
T16431831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Sample Return campaign |
E399086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planetary sample-return 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: planetary sample-return program Context triple: [Mars Sample Return campaign, instanceOf, planetary sample-return program]
-
A.
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.
-
B.
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.
-
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.
spacecraft program
A spacecraft program is an organized, long-term initiative that plans, develops, launches, and operates one or more spacecraft to achieve specific scientific, commercial, or exploratory objectives.
-
E.
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.
- 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.