Triple
T38645772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Asia–Southeast Asia air corridor |
E938710
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international flight route system |
C25851
|
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: international flight route system Context triple: [East Asia–Southeast Asia air corridor, instanceOf, international flight route system]
-
A.
international air route
chosen
An international air route is a designated flight path that connects airports in different countries, governed by bilateral or multilateral agreements and aviation regulations.
-
B.
airline network
An airline network is a system of interconnected routes, airports, and flights that enables the transportation of passengers and cargo between multiple destinations.
-
C.
long-distance flight route
A long-distance flight route is a regularly scheduled air travel path that covers a substantial geographic span, typically connecting distant cities or regions across countries or continents.
-
D.
transcontinental air route
A transcontinental air route is a regularly operated flight path that connects airports on different continents, enabling long-distance international air travel across major landmasses or oceans.
-
E.
international air travel market
The international air travel market is the global system in which airlines, passengers, regulators, and related service providers interact to supply and demand cross-border air transportation services, with prices and capacity shaped by competition, regulation, economic conditions, and geopolitical factors.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.