Triple
T33211692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Space Force Eastern Range and Western Range system |
E850179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space launch range system |
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 range system Context triple: [United States Space Force Eastern Range and Western Range system, instanceOf, space launch range system]
-
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 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.
-
C.
spacecraft launch interface
A spacecraft launch interface is the coordinated set of hardware, software, and procedural elements that connect a launch vehicle, payload, and ground systems to manage and control all functions leading up to and during liftoff.
-
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 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.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:30 a.m.