Triple
T38092164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USOS |
E951143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | orbital space station module segment |
C36605
|
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: orbital space station module segment Context triple: [USOS, instanceOf, orbital space station module segment]
-
A.
orbital space station
An orbital space station is a large, habitable artificial structure that continuously orbits a celestial body, serving as a long-term platform for human presence, research, and operations in space.
-
B.
space station segment group
chosen
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.
-
C.
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.
-
D.
International Space Station truss segment
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.
-
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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.