Triple

T3888883
Position Surface form Disambiguated ID Type / Status
Subject Pax Mongolica E88009 entity
Predicate instanceOf P0 FINISHED
Object transcontinental trade system 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: transcontinental trade system
Context triple: [Pax Mongolica, instanceOf, transcontinental trade system]
  • 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. 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.
  • C. 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.
  • D. transcontinental automobile route
    A transcontinental automobile route is a long-distance roadway or network of connected highways that enables continuous vehicular travel across an entire continent from one coast or border to another.
  • E. transcontinental city
    A transcontinental city is an urban area whose continuous metropolitan territory spans across two or more continents, often divided by a major geographic boundary such as a strait, sea, or continental border.
  • 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.