Triple
T26726832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMU backpack |
E673857
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronaut propulsion unit |
C22524
|
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: astronaut propulsion unit Context triple: [MMU backpack, instanceOf, astronaut propulsion unit]
-
A.
astronaut propulsion system
chosen
An astronaut propulsion system is a compact, controllable device that enables astronauts to maneuver independently in space by generating thrust through expelled propellant or alternative reaction-mass technologies.
-
B.
modular spacecraft
A modular spacecraft is a reconfigurable space vehicle composed of interchangeable, standardized modules that can be assembled, upgraded, or replaced to support different missions and functions.
-
C.
space launch vehicle component
A space launch vehicle component is a physical subsystem or part—such as engines, tanks, avionics, or structural elements—that contributes to the propulsion, guidance, structural integrity, or support functions required to deliver payloads from Earth to space.
-
D.
spacecraft service module
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.
-
E.
rocket booster
A rocket booster is a powerful propulsion component that provides the initial thrust needed to lift a launch vehicle off the ground and accelerate it through the early stages of flight.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:43 a.m.