Triple

T14138137
Position Surface form Disambiguated ID Type / Status
Subject Europe–Africa transport network E350352 entity
Predicate instanceOf P0 FINISHED
Object logistics corridor system 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: logistics corridor system
Context triple: [Europe–Africa transport network, instanceOf, logistics corridor system]
  • 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. 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.
  • C. trade and transportation corridor initiative
    A trade and transportation corridor initiative is a coordinated program to develop and optimize key routes, infrastructure, and policies that facilitate efficient movement of goods and people across regions or borders.
  • D. 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.
  • E. transportation corridors collection
    A transportation corridors collection is an organized set of linear pathways—such as roads, railways, and transit routes—grouped for managing, analyzing, or planning movement across a region.
  • 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_69d827865f608190b311820428ae027b completed April 9, 2026, 10:26 p.m.
Created at: April 10, 2026, 12:39 a.m.