Triple
T13553227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunshield and Interface Structure |
E323701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | thermal protection system |
C10279
|
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: thermal protection system Context triple: [Sunshield and Interface Structure, instanceOf, thermal protection system]
-
A.
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.
-
B.
heat shield material
chosen
A heat shield material is a specialized substance engineered to withstand and dissipate extreme thermal loads, protecting underlying structures from high temperatures and thermal damage.
-
C.
astronaut propulsion system
An astronaut propulsion system is a compact, controllable device that enables astronauts to maneuver independently in space by generating thrust through expelled propellant or alternative reaction-mass technologies.
-
D.
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.
-
E.
expendable launch system
An expendable launch system is a type of launch vehicle designed for a single use, where major components are not recovered after delivering payloads such as satellites or spacecraft into orbit or on a trajectory.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:46 p.m.