Triple
T32318823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO Chapter 4 |
E825714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation noise regulation |
C5730
|
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 noise regulation Context triple: [ICAO Chapter 4, instanceOf, aviation noise regulation]
-
A.
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.
-
B.
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.
-
C.
aviation regulatory framework
chosen
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.
-
D.
aviation law
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.
-
E.
aviation infrastructure plan
An aviation infrastructure plan is a strategic blueprint that outlines the development, expansion, maintenance, and integration of airport facilities, airspace systems, and supporting services to safely and efficiently meet current and future air transportation needs.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:46 a.m.