Triple
T13377732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmic Background Explorer |
E319232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cosmology mission |
C8801
|
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: cosmology mission Context triple: [Cosmic Background Explorer, instanceOf, cosmology mission]
-
A.
space mission
chosen
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.
cosmology experiment
A cosmology experiment is a scientific investigation designed to measure and analyze cosmic phenomena—such as the cosmic microwave background, large-scale structure, or dark energy—to test and refine models of the universe’s origin, composition, and evolution.
-
C.
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.
-
D.
space science programme
A space science programme is an organized set of research, missions, and educational activities focused on exploring and understanding space, celestial bodies, and related physical phenomena.
-
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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:33 p.m.