Triple
T27343254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Lightweight Tank |
E684166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Space Shuttle external tank variant |
C27328
|
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 external tank variant Context triple: [Super Lightweight Tank, instanceOf, Space Shuttle external tank variant]
-
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.
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.
-
C.
Saturn V mobile launcher
The Saturn V mobile launcher was a massive, self-contained launch platform and service structure that transported, supported, and provided umbilical connections to the Saturn V rocket from assembly to liftoff.
-
D.
Space Shuttle subsystem
chosen
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.
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.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:44 a.m.