Triple
T26423455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Sea trade network |
E664303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical trade system |
C47374
|
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 system Context triple: [North Sea trade network, instanceOf, historical trade system]
-
A.
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.
-
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.
trade system
chosen
A trade system is a structured framework of rules, mechanisms, and participants that enables the exchange of goods, services, or assets between parties, often across regions or markets.
-
D.
ancient trade route
An ancient trade route is a historically established pathway or network used for the long-distance exchange of goods, ideas, cultures, and technologies between regions and civilizations.
-
E.
colonial-era trade corridor
A colonial-era trade corridor is a strategically established route or network used during colonial times to transport goods, people, and resources between colonies and imperial centers, shaping economic patterns and cultural exchanges.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:44 p.m.