Triple
T18487244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATLAS-1 |
E451721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | solar science 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: solar science mission Context triple: [ATLAS-1, instanceOf, solar science mission]
-
A.
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.
-
B.
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.
-
C.
heliophysics mission fleet
A heliophysics mission fleet is a coordinated collection of spacecraft and instruments designed to observe the Sun and its interactions with the solar system from multiple vantage points to better understand solar activity and space weather.
-
D.
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.
-
E.
space science division
The space science division is an organizational unit dedicated to researching, analyzing, and advancing knowledge about outer space, celestial bodies, and related physical phenomena.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:35 a.m.