Triple
T13538580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPE (Power and Propulsion Element) |
E323323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | power and propulsion 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: power and propulsion module Context triple: [PPE (Power and Propulsion Element), instanceOf, power and propulsion module]
-
A.
spacecraft power system
A spacecraft power system is the integrated set of components and subsystems that generate, store, condition, and distribute electrical energy to support all spacecraft functions throughout its mission.
-
B.
astronaut propulsion system
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.
-
C.
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.
-
D.
nuclear pulse propulsion system
A nuclear pulse propulsion system is a spacecraft propulsion method that generates thrust by detonating a series of small nuclear explosives behind the vehicle and transferring the resulting impulse through a robust pusher plate and shock-absorbing structure.
-
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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:45 p.m.