Triple
T10501510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endeavour |
E247682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Apollo command and service module |
C2827
|
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: Apollo command and service module Context triple: [Endeavour, instanceOf, Apollo command and service module]
-
A.
Apollo Lunar Module
The Apollo Lunar Module was a two-stage, crewed spacecraft designed exclusively for lunar orbit operations and surface landings during NASA's Apollo missions.
-
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 capsule
chosen
A space capsule is a small, often conical or cylindrical crew or cargo spacecraft designed to survive launch, spaceflight, reentry, and landing while protecting its occupants and equipment.
-
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.
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.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:25 p.m.