Triple
T9713572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volga trade route |
E235080
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river trade network |
C6053
|
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: river trade network Context triple: [Volga trade route, instanceOf, river trade network]
-
A.
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.
-
B.
waterway network
chosen
A waterway network is an interconnected system of natural and artificial water channels (such as rivers, canals, and streams) designed or utilized for the movement, distribution, and management of water and waterborne transport.
-
C.
Infrastructure for trade
Infrastructure for trade encompasses the physical, digital, and institutional systems—such as transportation networks, ports, logistics hubs, communication technologies, and regulatory frameworks—that enable the efficient exchange of goods and services across regions and markets.
-
D.
medieval trading network
A medieval trading network is an interconnected system of routes, markets, and merchants that facilitated the exchange of goods, money, and information across regions during the Middle Ages.
-
E.
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.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:19 p.m.