Triple
T20098322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anchorage–Nome region |
E496464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air transport corridor |
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: air transport corridor Context triple: [Anchorage–Nome region, instanceOf, air transport corridor]
-
A.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
B.
air transport connection
An air transport connection is a scheduled or unscheduled linkage between two or more locations by aircraft, enabling the movement of passengers or cargo within an air transportation network.
-
C.
international air route
An international air route is a designated flight path that connects airports in different countries, governed by bilateral or multilateral agreements and aviation regulations.
-
D.
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.
-
E.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:25 p.m.