Triple
T26529749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neurolab Spacelab module |
E670786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spacelab module |
C26340
|
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: Spacelab module Context triple: [Neurolab Spacelab module, instanceOf, Spacelab module]
-
A.
Spacelab subsystem
A Spacelab subsystem is a distinct functional component of the Spacelab space laboratory that performs specialized tasks—such as power, life support, data handling, or experiment support—to enable and sustain scientific operations in orbit.
-
B.
Space Shuttle payload module
chosen
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.
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.
-
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.
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.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:34 a.m.