Triple
T38685339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISS Flight 8A |
E949100
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Space Shuttle mission segment |
C5891
|
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 Shuttle mission segment Context triple: [ISS Flight 8A, instanceOf, Space Shuttle mission segment]
-
A.
Space Shuttle mission
chosen
A Space Shuttle mission is a coordinated spaceflight operation using the Space Shuttle orbiter to transport crew, cargo, and conduct scientific or technical objectives in Earth orbit and beyond.
-
B.
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.
-
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 orbiter
A space shuttle orbiter is a reusable winged spacecraft designed to carry crew and cargo to and from low Earth orbit, operate as an orbital laboratory or platform, and then re-enter the atmosphere and land like an airplane.
-
E.
Space Shuttle payload
A Space Shuttle payload is any cargo, equipment, satellite, experiment, or module carried in the Shuttle’s payload bay to be deployed, operated, or returned from space.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.