Triple
T32075045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 transporter-erector |
E819120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | launch pad infrastructure |
C32735
|
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: launch pad infrastructure Context triple: [Falcon 9 transporter-erector, instanceOf, launch pad infrastructure]
-
A.
space launch facility
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.
spaceport facility
A spaceport facility is a complex of specialized infrastructure and services designed to support the launch, landing, maintenance, and logistical operations of spacecraft and their crews.
-
C.
spaceport facility component
chosen
A spaceport facility component is an individual physical or functional element—such as launch pads, control centers, fueling systems, or passenger terminals—that collectively enables the operation, support, and management of spaceflight activities at a spaceport.
-
D.
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.
-
E.
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.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:23 a.m.