Triple
T13553135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Magnetospheric Orbiter |
E323699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planetary science mission element |
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 element Context triple: [Mercury Magnetospheric Orbiter, instanceOf, planetary science mission element]
-
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.
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.
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.
-
D.
space mission study
A space mission study is a systematic analysis and planning effort that defines the objectives, feasibility, design options, costs, risks, and expected outcomes of a proposed space mission before it proceeds to development.
-
E.
space mission science team
A space mission science team is a multidisciplinary group of scientists and specialists responsible for defining mission objectives, designing experiments, analyzing data, and interpreting scientific results to achieve the mission’s research goals.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:46 p.m.