Triple
T33549791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 14 CFR Part 135 |
E859302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Federal Aviation Regulation |
C8365
|
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: U.S. Federal Aviation Regulation Context triple: [14 CFR Part 135, instanceOf, U.S. Federal Aviation Regulation]
-
A.
U.S. Department of Transportation regulation
A U.S. Department of Transportation regulation is a legally binding rule issued by the DOT that governs the safe, efficient, and accessible operation of the nation’s transportation systems and related activities.
-
B.
aviation regulatory framework
The aviation regulatory framework is the structured set of laws, standards, and oversight mechanisms that govern the safe, efficient, and environmentally responsible operation of civil aviation activities.
-
C.
Federal Aviation Administration publication
chosen
A Federal Aviation Administration publication is an official document issued by the FAA that provides regulations, standards, procedures, guidance, or informational material related to civil aviation safety and operations in the United States.
-
D.
aviation regulatory decision
An aviation regulatory decision is an authoritative ruling or policy issued by a competent aviation authority that defines, interprets, or enforces rules governing the safety, operation, certification, or oversight of civil aviation activities.
-
E.
aviation authority
An aviation authority is a governmental or regulatory body responsible for overseeing civil aviation safety, security, standards, and compliance within a specific jurisdiction.
- 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.