Triple
T37720793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-1 launch vehicle |
E939576
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reusable launch vehicle |
C62965
|
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 launch vehicle Context triple: [K-1 launch vehicle, instanceOf, reusable launch vehicle]
-
A.
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.
-
B.
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.
-
C.
reusable suborbital launch vehicle
A reusable suborbital launch vehicle is a spacecraft designed to carry payloads or passengers to the edge of space and return safely for multiple flights, reducing the cost and turnaround time of suborbital missions.
-
D.
expendable launch vehicle
An expendable launch vehicle is a rocket designed for a single use to deliver payloads such as satellites or spacecraft into space, after which its components are discarded rather than recovered or reused.
-
E.
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.
- F. None of above. chosen
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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.