Triple
T32282586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSPE |
E824740
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planetary science mission component |
C33205
|
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 component Context triple: [LSPE, instanceOf, planetary science mission component]
-
A.
planetary science mission element
chosen
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.
-
B.
NASA mission component
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
C.
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.
-
D.
Mars system mission
A Mars system mission is a spaceflight endeavor designed to explore Mars and its surrounding environment, including its moons, atmosphere, surface, and potential for past or present life.
-
E.
Mars mission element
A Mars mission element is a distinct component, system, or phase of a Mars exploration mission (such as spacecraft, landers, habitats, or support infrastructure) that contributes specific functions toward achieving the mission’s overall 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:43 a.m.