Triple
T37941483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSL-1 |
E946499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | microgravity 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: microgravity science mission Context triple: [MSL-1, instanceOf, microgravity science mission]
-
A.
space experiment
A space experiment is a controlled scientific investigation conducted in the unique conditions of outer space or microgravity to study physical, biological, or technological phenomena not observable or easily replicated on Earth.
-
B.
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.
-
C.
scientific payload
A scientific payload is the collection of instruments, sensors, and supporting equipment carried by a vehicle (such as a satellite, rocket, or aircraft) specifically to conduct experiments and gather scientific data.
-
D.
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.
-
E.
space mission science team
A space mission science team is a multidisciplinary group of scientists and specialists responsible for defining mission objectives, designing experiments, analyzing data, and interpreting scientific results to achieve the mission’s research goals.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.