Triple
T7779568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU–US Open Skies Agreement |
E221478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open skies agreement |
C824
|
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: open skies agreement Context triple: [EU–US Open Skies Agreement, instanceOf, open skies agreement]
-
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.
ozone protection agreement
An ozone protection agreement is a formal international or regional accord that commits participating parties to regulate and reduce substances and activities that deplete the Earth’s ozone layer.
-
C.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
D.
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.
-
E.
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.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 4:19 p.m.