Triple
T38059647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish UIR |
E950304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airspace sector |
C61030
|
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 sector Context triple: [Scottish UIR, instanceOf, airspace sector]
-
A.
airspace security operation
An airspace security operation is a coordinated set of activities, technologies, and procedures designed to monitor, control, and protect designated airspace from unauthorized or hostile aerial threats.
-
B.
airspace management region
chosen
An airspace management region is a defined volume of airspace within which air traffic and related activities are coordinated, controlled, and regulated according to specific operational rules and responsibilities.
-
C.
airspace governance framework
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.
-
D.
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.
-
E.
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.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.