Triple
T21135006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA HL-20 lifting-body design |
E520794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crewed reentry vehicle concept |
C5707
|
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: crewed reentry vehicle concept Context triple: [NASA HL-20 lifting-body design, instanceOf, crewed reentry vehicle concept]
-
A.
prototype re-entry vehicle
A prototype re-entry vehicle is an experimental spacecraft or missile body designed to test and validate technologies, materials, and aerothermal performance for surviving high-speed descent through a planetary atmosphere.
-
B.
reusable spaceplane
chosen
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.
ablative thermal protection system
An ablative thermal protection system is a heat shield that protects a spacecraft by sacrificially charring, melting, and eroding material to absorb and carry away extreme reentry heat.
-
D.
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.
-
E.
space capsule
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.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:56 p.m.