Triple

T14754224
Position Surface form Disambiguated ID Type / Status
Subject Baltic Sea trade routes E346688 entity
Predicate instanceOf P0 FINISHED
Object riverine trade route system 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 trade route system
Context triple: [Baltic Sea trade routes, instanceOf, riverine trade route system]
  • 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. ancient trade route
    An ancient trade route is a historically established pathway or network used for the long-distance exchange of goods, ideas, cultures, and technologies between regions and civilizations.
  • C. transoceanic trade network
    A transoceanic trade network is a system of interconnected maritime routes, ports, merchants, and institutions that facilitate the large-scale exchange of goods, people, capital, and ideas across oceans between distant regions of the world.
  • D. transalpine trade route
    A transalpine trade route is a transportation corridor that crosses the Alps to facilitate the movement of goods, people, and cultural exchange between regions on either side of the mountain range.
  • E. Indigenous travel corridor
    An Indigenous travel corridor is a traditional route or network of pathways used by Indigenous peoples for movement, trade, cultural exchange, and connection across their ancestral lands.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
Created at: April 10, 2026, 1:30 a.m.