Triple
T32746441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaction Control System |
E837365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft propulsion subsystem |
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: spacecraft propulsion subsystem Context triple: [Reaction Control System, instanceOf, spacecraft propulsion subsystem]
-
A.
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.
-
B.
spacecraft propulsion concept
A spacecraft propulsion concept is a theoretical or practical method for generating thrust to maneuver a spacecraft in space, encompassing the underlying physics, required systems, and performance characteristics.
-
C.
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.
-
D.
rocket propulsion system family
A rocket propulsion system family is a group of related propulsion system designs that share common architecture, components, and performance characteristics, enabling scalable thrust and mission-specific configurations.
-
E.
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.
- F. None of above. chosen
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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:12 a.m.