Triple
T21923117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin Flight Information Region |
E541370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Airspace region |
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: Airspace region Context triple: [Dublin Flight Information Region, instanceOf, Airspace region]
-
A.
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.
-
B.
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.
-
C.
strategic airspace
Strategic airspace is a designated portion of the sky managed and controlled to support long-term military, security, or national policy objectives, including surveillance, defense, and power projection.
-
D.
airport flight path area
The airport flight path area is the three-dimensional airspace corridor surrounding an airport that aircraft use for approach, landing, takeoff, and initial climb or departure, governed by safety, noise, and air traffic control constraints.
-
E.
uncontrolled airspace
Uncontrolled airspace is a portion of the atmosphere where air traffic control services are not provided to all aircraft, and pilots are primarily responsible for seeing and avoiding other traffic while following applicable regulations.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:45 p.m.