Triple
T16807581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Launch Services |
E408518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial space launch company |
C14045
|
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: commercial space launch company Context triple: [International Launch Services, instanceOf, commercial space launch company]
-
A.
space services company
chosen
A space services company is an organization that provides commercial solutions related to space activities, such as launch services, satellite deployment and operations, in-orbit logistics, data services, and mission support for government, commercial, and research customers.
-
B.
space tourism company
A space tourism company is an organization that offers commercial travel experiences beyond Earth's atmosphere, providing customers with short-term spaceflights, orbital stays, or related extraterrestrial adventures.
-
C.
rocket manufacturer
A rocket manufacturer is a company or organization that designs, builds, tests, and supplies rockets and related launch systems for commercial, scientific, or governmental use.
-
D.
commercial spaceflight regulation
Commercial spaceflight regulation is the body of laws, policies, and oversight mechanisms that govern the safety, licensing, operations, and liability of private entities conducting spaceflight activities.
-
E.
space charter
A space charter is a contractual agreement that grants an individual or organization the exclusive right to use a spacecraft or space transport service for a specified mission, route, time period, or set of conditions.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.