Triple
T33504596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Flight Rules Area |
E858079
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation regulatory concept |
C5729
|
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 regulatory concept Context triple: [Special Flight Rules Area, instanceOf, aviation regulatory concept]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
airspace governance framework
chosen
An airspace governance framework is a structured set of policies, regulations, and institutional arrangements that define how airspace is allocated, managed, monitored, and enforced to ensure safe, efficient, and equitable use by all airspace users.
-
E.
aviation convention
An aviation convention is a large organized gathering of aviation professionals, enthusiasts, and industry stakeholders to showcase aircraft, technologies, services, and to exchange knowledge through exhibitions, presentations, and networking events.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.