Triple
T14418876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle approach and landing tests |
E357527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Space Shuttle test program |
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 test program Context triple: [Space Shuttle approach and landing tests, instanceOf, Space Shuttle test program]
-
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 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.
NASA rocket engine test facility
A NASA rocket engine test facility is a specialized complex equipped with infrastructure, instrumentation, and safety systems to ground-test and validate rocket engines under controlled, flight-like conditions.
-
D.
Space Shuttle Endeavour
Space Shuttle Endeavour is a retired NASA orbiter that served as a reusable spacecraft for transporting astronauts, satellites, and scientific payloads to and from low Earth orbit as part of the Space Shuttle program.
-
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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.