Triple
T15880654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Space Station modules (NASA segments) |
E385066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space station segment group |
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: space station segment group Context triple: [International Space Station modules (NASA segments), instanceOf, space station segment group]
-
A.
crewed space station
A crewed space station is a permanently or semi-permanently inhabited orbital facility that supports human life and scientific, technological, or operational activities in space.
-
B.
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.
-
C.
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.
-
D.
Space Shuttle subsystem
A Space Shuttle subsystem is a distinct functional component or collection of components within the Space Shuttle that performs a specific role—such as propulsion, life support, guidance, or power management—to enable safe and effective mission operations.
-
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. 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.