Triple
T22261716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Aeronautics Board Sunset Act of 1984 |
E550241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation-related legislation |
C4625
|
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: aviation-related legislation Context triple: [Civil Aeronautics Board Sunset Act of 1984, instanceOf, aviation-related legislation]
-
A.
aviation law
chosen
Aviation law is the body of rules, regulations, and international agreements that govern the operation, safety, security, and economic aspects of air travel and aircraft use.
-
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.
aviation policy initiative
An aviation policy initiative is a coordinated effort, typically led by governments or industry bodies, to develop, reform, or implement rules and strategies that shape the safety, efficiency, sustainability, and economic regulation of air transport systems.
-
D.
aviation liability convention
An aviation liability convention is an international legal agreement that standardizes rules for airlines’ financial responsibility and compensation for passengers, cargo, and third parties in the event of accidents or incidents in air transport.
-
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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:39 p.m.