Triple

T1368650
Position Surface form Disambiguated ID Type / Status
Subject Scandinavia–Russia transport corridor E30059 entity
Predicate instanceOf P0 FINISHED
Object international transport corridor C2952 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 transport corridor
Context triple: [Scandinavia–Russia transport corridor, instanceOf, international transport corridor]
  • A. transport corridor chosen
    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. 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.
  • C. international border crossing
    An international border crossing is a designated point where people, goods, and vehicles are legally inspected and allowed to pass between two countries.
  • D. freight rail corridor
    A freight rail corridor is a designated railway route primarily used for the efficient, high-capacity movement of goods and cargo between industrial, commercial, and logistics hubs.
  • E. road–rail border crossing
    A road–rail border crossing is a designated point at an international boundary where both road and railway transport routes intersect or pass through, enabling the controlled movement of vehicles, trains, goods, and passengers between neighboring countries.
  • 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_69a498f912008190a376a98b207b2071 completed March 1, 2026, 7:52 p.m.
Created at: March 1, 2026, 7:57 p.m.