Triple
T30731242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention Relating to the Regulation of Aerial Navigation |
E782428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air law instrument |
C41428
|
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: air law instrument Context triple: [Convention Relating to the Regulation of Aerial Navigation, instanceOf, air law instrument]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
aviation liability convention
chosen
An aviation liability convention is an international legal agreement that standardizes rules for airlines’ financial responsibility and compensation for passengers, cargo, and third parties in the event of accidents or incidents in air transport.
-
E.
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.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:37 p.m.