Triple
T13256509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA’s Launch Services infrastructure |
E315671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space launch infrastructure |
C5843
|
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 launch infrastructure Context triple: [NASA’s Launch Services infrastructure, instanceOf, space launch infrastructure]
-
A.
space launch facility
chosen
A space launch facility is a specialized complex equipped with infrastructure, systems, and support services for preparing, launching, and sometimes recovering spacecraft and launch vehicles.
-
B.
space launch support vehicle
A space launch support vehicle is a specialized ground or aerial platform that transports, positions, services, and supports rockets or spacecraft before and during launch operations.
-
C.
orbital launch vehicle
An orbital launch vehicle is a rocket-powered system designed to transport payloads from Earth's surface into orbit by achieving sufficient velocity and altitude to remain in continuous free-fall around the planet.
-
D.
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.
-
E.
space access mission area
The space access mission area encompasses the systems, operations, and infrastructure required to reliably and affordably deliver payloads and humans from Earth to space and between orbital or celestial destinations.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:24 p.m.