Triple
T38271998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interflug agricultural aviation division |
E1021236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of airline |
C66090
|
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: subdivision of airline Context triple: [Interflug agricultural aviation division, instanceOf, subdivision of airline]
-
A.
regional airline
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.
airline category
An airline category represents a classification of airlines based on shared characteristics such as service level, business model, route network, or regulatory designation.
-
C.
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.
-
D.
domestic airline operation
A domestic airline operation is the coordinated management and execution of air transportation services within a single country, including flight scheduling, crew and aircraft assignment, ground handling, and regulatory compliance.
-
E.
business aviation company division
A business aviation company division is an organizational unit within a larger aviation enterprise that focuses on providing private air travel services, fleet management, and related support specifically for corporate and high-net-worth clients.
- F. None of above. chosen
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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.