Triple
T3452650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediterranean trade routes |
E72828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime trade route system |
C2569
|
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: maritime trade route system Context triple: [Mediterranean trade routes, instanceOf, maritime trade route 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.
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.
-
C.
sea route
chosen
A sea route is a navigable path across seas or oceans used by ships to travel between ports for trade, transport, or exploration.
-
D.
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.
-
E.
maritime convoy system
A maritime convoy system is an organized method of grouping merchant or military vessels to sail together under coordinated protection and navigation to reduce risks from threats such as enemy attacks, piracy, or hazardous conditions.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:16 p.m.