Triple
T22877409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamchatka Civil Aviation Authority |
E567361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional aviation regulator |
C1857
|
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: regional aviation regulator Context triple: [Kamchatka Civil Aviation Authority, instanceOf, regional aviation regulator]
-
A.
regional aviation organization
A regional aviation organization is an entity that coordinates, regulates, and promotes air transport services and infrastructure within a specific geographic area to ensure safe, efficient, and sustainable aviation operations.
-
B.
aviation authority
chosen
An aviation authority is a governmental or regulatory body responsible for overseeing civil aviation safety, security, standards, and compliance within a specific jurisdiction.
-
C.
regional aviation industry
The regional aviation industry encompasses airlines, airports, manufacturers, and service providers that operate and support short- to medium-haul air transport connecting smaller cities and communities to larger hubs.
-
D.
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.
-
E.
aviation infrastructure organization
An aviation infrastructure organization is an entity responsible for planning, developing, operating, and maintaining the physical and technological systems that support air transportation, such as airports, air traffic control, and related facilities.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:39 p.m.