Triple
T13173368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LunIR CubeSat |
E313033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | deep-space technology demonstration mission |
C9136
|
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: deep-space technology demonstration mission Context triple: [LunIR CubeSat, instanceOf, deep-space technology demonstration mission]
-
A.
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.
-
B.
space technology
Space technology encompasses the tools, systems, and methods used to explore, utilize, and operate in outer space, including spacecraft, satellites, launch vehicles, and supporting ground infrastructure.
-
C.
space technology
Space technology encompasses the tools, systems, and methods developed to explore, utilize, and operate in outer space, including spacecraft, satellites, launch vehicles, and supporting ground infrastructure.
-
D.
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.
-
E.
interplanetary space mission
chosen
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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:14 p.m.