Triple
T26847925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P3/P4 truss segment |
E675975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space station truss segment |
C46713
|
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: space station truss segment Context triple: [P3/P4 truss segment, instanceOf, space station truss segment]
-
A.
International Space Station truss segment
chosen
An International Space Station truss segment is a structural module that forms part of the station’s backbone, supporting solar arrays, radiators, and utilities while providing attachment points and routing for power, data, and thermal control systems.
-
B.
Space Shuttle payload module
A Space Shuttle payload module is a specialized, modular structure designed to house, support, and interface scientific instruments, cargo, or satellites within the Shuttle’s payload bay for deployment or on-orbit operations.
-
C.
space station segment group
A space station segment group is a collection of interconnected modules or structural elements that function together as a cohesive subsystem within a larger space station.
-
D.
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.
-
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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:14 a.m.