Triple
T38645773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Asia–Southeast Asia air corridor |
E938710
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation route network |
C31875
|
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: aviation route network Context triple: [East Asia–Southeast Asia air corridor, instanceOf, aviation route network]
-
A.
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.
-
B.
aviation infrastructure network
An aviation infrastructure network is an interconnected system of airports, airways, navigation aids, communication systems, and support facilities that collectively enable the safe, efficient movement of aircraft and passengers.
-
C.
regional air route
chosen
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.
-
D.
airport flight path area
The airport flight path area is the three-dimensional airspace corridor surrounding an airport that aircraft use for approach, landing, takeoff, and initial climb or departure, governed by safety, noise, and air traffic control constraints.
-
E.
aviation organization network
An aviation organization network is a structured system of interconnected aviation-related entities—such as airlines, airports, regulators, manufacturers, and service providers—that collaborate and exchange information, resources, and services to support and optimize air transport operations.
- 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.