Triple
T1523449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Transportation System |
E32281
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reusable spacecraft program |
C1125
|
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: reusable spacecraft program Context triple: [Space Transportation System, instanceOf, reusable spacecraft program]
-
A.
reusable spaceplane
A reusable spaceplane is a winged spacecraft designed to take off, operate, and land multiple times like an aircraft while transporting payloads or crew between Earth and space.
-
B.
fully reusable launch system
A fully reusable launch system is a space launch architecture in which all major components (such as boosters, upper stages, and spacecraft) are recovered, refurbished, and flown again, minimizing expendable hardware and reducing per-launch costs.
-
C.
human spaceflight program
chosen
A human spaceflight program is an organized, long-term governmental or commercial initiative that designs, funds, and operates crewed missions beyond Earth’s atmosphere for exploration, research, and related objectives.
-
D.
partially reusable launch vehicle
A partially reusable launch vehicle is a space launch system in which only some components—such as the first stage, boosters, or engines—are recovered and refurbished for multiple flights, while the remaining parts are expended.
-
E.
space transportation system
A space transportation system is an integrated set of vehicles, infrastructure, and operations designed to move payloads and passengers between Earth and space or between locations in 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.