Triple
T1399374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Passage |
E30745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | segment of the Atlantic slave trade |
C3009
|
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: segment of the Atlantic slave trade Context triple: [Middle Passage, instanceOf, segment of the Atlantic slave trade]
-
A.
slave trade site
A slave trade site is a historical location where enslaved people were captured, held, bought, sold, or transported as part of the transatlantic or other slave trading systems.
-
B.
transatlantic trade system
chosen
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.
British slave-trading company
A British slave-trading company is a commercial enterprise, chartered or based in Britain, that organized, financed, and profited from the capture, transport, and sale of enslaved Africans across the Atlantic.
-
D.
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.
-
E.
transatlantic migration
Transatlantic migration is the large-scale movement of people across the Atlantic Ocean, historically and contemporarily, driven by economic, political, social, and environmental factors that reshape societies on both sides.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.