Triple
T2229494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington DC Special Flight Rules Area |
E48730
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special flight rules area |
C2156
|
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: special flight rules area Context triple: [Washington DC Special Flight Rules Area, instanceOf, special flight rules area]
-
A.
regulated airspace
chosen
Regulated airspace is a defined volume of the atmosphere where aircraft operations are subject to specific rules, restrictions, and oversight by aviation authorities to ensure safety and orderly traffic flow.
-
B.
national airspace
National airspace is the three-dimensional region of the atmosphere above a country's territory and territorial waters over which that nation exercises legal jurisdiction, regulation, and control of aircraft operations.
-
C.
air navigation organization
An air navigation organization is an entity responsible for planning, managing, and controlling the safe and efficient movement of aircraft through designated airspace using air traffic services, communication, navigation, and surveillance systems.
-
D.
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.
-
E.
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.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:47 p.m.