Triple
T33549841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 14 CFR Part 420 |
E859303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial space transportation 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 space transportation regulation Context triple: [14 CFR Part 420, instanceOf, commercial space transportation regulation]
-
A.
commercial spaceflight regulation
chosen
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.
-
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.
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.
-
D.
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.
-
E.
space law instrument
A space law instrument is a formal legal document—such as a treaty, agreement, or regulation—that establishes rules and principles governing activities and relationships in outer space and related celestial environments.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.