Triple
T12185306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager imaging team |
E290318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space mission science team |
C31045
|
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 science team Context triple: [Voyager imaging team, instanceOf, space mission science team]
-
A.
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.
-
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.
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.
NASA mission component
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
E.
Mars mission engineering activity
Mars mission engineering activity encompasses the planning, design, testing, and integration of systems and technologies required to safely transport, land, and support missions on the Martian surface and in its orbit.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:50 p.m.