Triple

T3888946
Position Surface form Disambiguated ID Type / Status
Subject Tea Horse Road E88010 entity
Predicate instanceOf P0 FINISHED
Object historical trade route network C12481 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: historical trade route network
Context triple: [Tea Horse Road, instanceOf, historical trade route network]
  • A. medieval trading network chosen
    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.
  • B. 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.
  • C. transatlantic trade system
    The transatlantic trade system was a network of economic exchanges linking Europe, Africa, and the Americas, involving the movement of goods, enslaved people, and raw materials across the Atlantic Ocean from the 16th to 19th centuries.
  • D. transport infrastructure network
    A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
  • E. maritime trading culture
    A maritime trading culture is a society whose economy, social structures, and worldview are fundamentally shaped by seafaring commerce, long-distance exchange, and coastal or port-based networks of interaction.
  • 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_69aed9466d548190939f5217a23ed4ac completed March 9, 2026, 2:29 p.m.
Created at: March 9, 2026, 3:21 p.m.