Triple
T18299008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Icarus |
E438306
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theoretical space mission study |
C15951
|
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: theoretical space mission study Context triple: [Project Icarus, instanceOf, theoretical space mission study]
-
A.
space mission study
chosen
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.
-
B.
planetary science mission element
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.
-
C.
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.
-
D.
interstellar spacecraft design study
A conceptual analysis and planning effort that explores, evaluates, and defines the technologies, configurations, and mission architectures required for a feasible interstellar spacecraft.
-
E.
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.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:35 a.m.