Triple
T13629511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvant-2 |
E325677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | life-support module |
C31816
|
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: life-support module Context triple: [Kvant-2, instanceOf, life-support module]
-
A.
spacecraft service module
chosen
A spacecraft service module is the section of a spacecraft that houses and provides essential support systems—such as propulsion, power, thermal control, and consumables—to enable and sustain the operation of the crew or payload module.
-
B.
extravehicular activity equipment
Extravehicular activity equipment comprises the specialized suits, life-support systems, tools, and safety devices that enable astronauts to work safely and effectively outside a spacecraft in the vacuum of space.
-
C.
space capsule
A space capsule is a small, often conical or cylindrical crew or cargo spacecraft designed to survive launch, spaceflight, reentry, and landing while protecting its occupants and equipment.
-
D.
in-situ resource utilization technology demonstrator
An in-situ resource utilization technology demonstrator is a prototype system designed to test and validate methods for extracting, processing, and using local materials (such as lunar or Martian regolith) to support space missions and reduce dependence on Earth-supplied resources.
-
E.
ablative thermal protection system
An ablative thermal protection system is a heat shield that protects a spacecraft by sacrificially charring, melting, and eroding material to absorb and carry away extreme reentry heat.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:51 p.m.