Triple
T23671237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assin Manso Slave River |
E584734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | slave trade heritage site |
C1182
|
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: slave trade heritage site Context triple: [Assin Manso Slave River, instanceOf, slave trade heritage site]
-
A.
slave trade site
chosen
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.
slave trader
A slave trader is a person or entity that profits from the buying, selling, and transporting of human beings as property, historically central to systems of chattel slavery and human exploitation.
-
C.
slave ship
A slave ship is a vessel specifically outfitted and used to forcibly transport enslaved people, typically under brutal and inhumane conditions, as part of the transatlantic slave trade.
-
D.
event in the transatlantic slave trade
An event in the transatlantic slave trade is a historically situated occurrence—such as a voyage, auction, rebellion, law, or treaty—that directly shaped the capture, transport, sale, resistance, or abolition of enslaved Africans across the Atlantic world.
-
E.
group of historic sites
A group of historic sites is a collection of geographically or thematically related locations that hold recognized cultural, architectural, or historical significance and are often managed or interpreted as a unified whole.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:50 p.m.