Triple
T14701271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeroflot Tyumen Directorate |
E345305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional airline directorate |
C1438
|
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 airline directorate Context triple: [Aeroflot Tyumen Directorate, instanceOf, regional airline directorate]
-
A.
regional airline
chosen
A regional airline is an air carrier that operates short-haul flights, typically connecting smaller cities or feeding passengers to larger hub airports using smaller aircraft.
-
B.
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.
-
C.
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.
-
D.
regional airline brand
A regional airline brand is a commercial identity used by an airline that operates short-haul flights within a specific geographic area, often under contract or in partnership with a larger national or international carrier.
-
E.
regional air route
A regional air route is a defined flight path connecting airports within a specific geographic area, typically served by short- to medium-haul aircraft to facilitate local or intra-regional air travel.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.