Triple
T8555508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Flagship Program |
E202553
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planetary science mission category |
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 category Context triple: [NASA Flagship Program, instanceOf, planetary science mission category]
-
A.
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.
-
B.
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.
-
C.
planetary science topic
A planetary science topic is a specific subject area focused on the physical, chemical, and geological properties, processes, and evolution of planets, moons, and other bodies in our solar system and beyond.
-
D.
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.
-
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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:19 p.m.