Triple
T13179151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Explorer program (beyond-Explorer class) |
E313679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space mission line |
C32589
|
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 mission line Context triple: [NASA Explorer program (beyond-Explorer class), instanceOf, space mission line]
-
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 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.
-
C.
interplanetary space mission
An interplanetary space mission is a coordinated endeavor that sends spacecraft from one planet to another to conduct scientific research, exploration, or technology demonstration beyond Earth's immediate environment.
-
D.
NASA space mission
A NASA space mission is a coordinated, goal-driven endeavor planned and executed by NASA to explore, observe, or utilize space using specialized spacecraft, instruments, and supporting ground operations.
-
E.
space communication project
A space communication project is an organized effort to design, develop, and operate systems that enable reliable data and signal exchange between spacecraft, satellites, and ground stations.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:14 p.m.