Triple

T34239231
Position Surface form Disambiguated ID Type / Status
Subject Vistula River trade route E878416 entity
Predicate instanceOf P0 FINISHED
Object riverine transport corridor C27647 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: riverine transport corridor
Context triple: [Vistula River trade route, instanceOf, riverine transport corridor]
  • A. riverine trade route chosen
    A riverine trade route is a navigable waterway along a river system used for the transport and exchange of goods, people, and cultural influences between settlements.
  • B. 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.
  • C. 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.
  • D. river corridor
    A river corridor is the linear landscape surrounding a river, including its channel, banks, floodplain, and adjacent habitats, through which water, sediment, organisms, and energy flow and interact.
  • E. 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.
  • 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_69f349b22d8c819096b22df268382aa9 completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 1:56 a.m.