Triple
T7210506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Heliophysics System Observatory missions |
E149388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space science mission program |
C15072
|
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: space science mission program Context triple: [NASA Heliophysics System Observatory missions, instanceOf, space science mission program]
-
A.
space mission
A space mission is a planned and coordinated endeavor to send spacecraft, instruments, or humans beyond Earth's atmosphere to achieve specific scientific, exploratory, commercial, or technological objectives.
-
B.
space exploration programme
chosen
A space exploration programme is an organized, long-term initiative that plans, funds, and conducts missions and research activities to explore outer space and expand scientific and technological knowledge.
-
C.
planetary exploration program
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.
-
D.
space technology development program
A space technology development program is an organized initiative that researches, designs, tests, and matures advanced space-related technologies to enable or enhance future space missions and capabilities.
-
E.
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.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:53 p.m.