Triple
T36223816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPE |
E1047927
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Power and Propulsion Element |
C60975
|
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 Element Context triple: [PPE, instanceOf, Power and Propulsion Element]
-
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.
spacecraft propulsion subsystem
chosen
A spacecraft propulsion subsystem is the integrated set of components and control mechanisms that generate and manage thrust to maneuver, orient, and adjust the trajectory of a spacecraft throughout its mission.
-
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 structural component
A spacecraft structural component is a physical element that forms part of the spacecraft’s load-bearing framework, providing mechanical support, alignment, and protection for onboard systems while withstanding launch and space environment stresses.
-
E.
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.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.