Triple
T12738331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Service Module |
E304422
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Orion spacecraft component |
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: Orion spacecraft component Context triple: [European Service Module, instanceOf, Orion spacecraft component]
-
A.
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.
-
B.
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.
-
C.
SpaceX launch vehicle component
A SpaceX launch vehicle component is a physical subsystem or part—such as engines, tanks, avionics, or structural elements—that integrates with other components to enable the safe, efficient, and reusable operation of a SpaceX rocket during all phases of flight.
-
D.
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.
-
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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.