Triple
T9807736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Space Launch Act |
E238194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial spaceflight regulation |
C26877
|
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 spaceflight regulation Context triple: [Commercial Space Launch Act, instanceOf, commercial spaceflight regulation]
-
A.
spaceflight safety initiative
A spaceflight safety initiative is a coordinated program of policies, technologies, and procedures designed to prevent accidents, protect crew and payloads, and ensure the safe operation of spacecraft throughout all mission phases.
-
B.
uncrewed spaceflight
Uncrewed spaceflight is the operation of spacecraft without human passengers onboard, using automated systems and remote control to conduct missions such as exploration, observation, and technology testing in space.
-
C.
orbital spaceflight
Orbital spaceflight is the process of launching a spacecraft into a stable, continuous orbit around a celestial body, typically Earth, by achieving sufficient horizontal velocity to balance gravitational pull.
-
D.
space operations
Space operations encompass the planning, execution, and management of activities involving spacecraft, satellites, and related systems to support missions such as communication, navigation, exploration, and defense in the space environment.
-
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. chosen
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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.