Triple
T35689688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remote Control Unit |
E1031254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacesuit component |
C22525
|
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: spacesuit component Context triple: [Remote Control Unit, instanceOf, spacesuit component]
-
A.
extravehicular activity equipment
chosen
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.
-
B.
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.
-
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.
spacewalker
A spacewalker is an individual who exits a spacecraft to perform tasks or exploration in the vacuum of space, typically wearing a specialized suit for life support and protection.
-
E.
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.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.