Triple

T17847839
Position Surface form Disambiguated ID Type / Status
Subject Principality of Smolensk E445709 entity
Predicate importantTradeRoutes P35626 FINISHED
Object Baltic–Byzantine trade route NE NERFINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Baltic–Byzantine trade route | Statement: [Principality of Smolensk, importantTradeRoutes, Baltic–Byzantine trade route]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baltic–Byzantine trade route
Context triple: [Principality of Smolensk, importantTradeRoutes, Baltic–Byzantine trade route]
  • A. Baltic Sea trade routes chosen
    The Baltic Sea trade routes were a network of maritime and riverine pathways that connected the cities and ports of Northern and Eastern Europe, facilitating extensive commerce in goods like furs, grain, and timber and linking regions such as the Novgorod Republic with the wider Hanseatic trading world.
  • B. White Sea trade route
    The White Sea trade route was a key maritime and riverine corridor in northern Russia that linked inland centers like Kholmogory to Arctic ports, facilitating early Russian trade with Western Europe.
  • C. Volga trade route
    The Volga trade route was a major medieval river and portage network linking Northern Europe and the Baltic to the Caspian Sea and the Islamic world, facilitating extensive commerce and cultural exchange.
  • D. Dnieper trade route
    The Dnieper trade route was a key medieval waterway used by Viking merchants to connect Northern Europe with the Byzantine Empire and the Black Sea region.
  • E. Vistula River trade route
    The Vistula River trade route was a major medieval and early modern commercial waterway in Central and Eastern Europe, facilitating the transport of goods—especially grain—from the Polish interior to Baltic Sea ports.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: importantTradeRoutes
Context triple: [Principality of Smolensk, importantTradeRoutes, Baltic–Byzantine trade route]
  • A. includesTradeRoute chosen
    Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
  • B. historicTradeRole
    Indicates that an entity historically functioned as a significant participant or hub in trade or commercial exchange.
  • C. eraOfStrategicImportance
    Indicates that a particular time period holds significant strategic value or influence within a broader historical, political, or organizational context.
  • D. historicalPeriodOfIntenseTrade
    Indicates a time span characterized by unusually high levels of trade activity between parties or regions.
  • E. portImportance
    Indicates the relative significance or strategic value of a port within a given context (such as trade, logistics, or transportation networks).
  • F. None of above.

Provenance (3 batches)

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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ffc5fec8190adc66f7b0e264d5f completed April 19, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69e3d8e266888190ae976b4b7d5b886f completed April 18, 2026, 7:17 p.m.
Created at: April 10, 2026, 10:16 a.m.