Triple
T29269296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA SIMPLEx missions |
E742066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planetary science mission 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 science mission program Context triple: [NASA SIMPLEx missions, instanceOf, planetary science mission program]
-
A.
planetary science program office
A planetary science program office is an organizational unit that plans, coordinates, and manages scientific missions, research activities, and resources focused on the study of planets, moons, and other bodies in the solar system and beyond.
-
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.
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.
-
D.
space science programme
A space science programme is an organized set of research, missions, and educational activities focused on exploring and understanding space, celestial bodies, and related physical phenomena.
-
E.
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.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:47 p.m.