Triple
T29786665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Cormantin |
E756283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Atlantic slave trade 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: Atlantic slave trade site Context triple: [Fort Cormantin, instanceOf, Atlantic slave trade 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.
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.
-
C.
ancient Nubian site
An ancient Nubian site is an archaeological location in the Nile Valley region of Nubia that preserves the material remains, architecture, and cultural landscapes of the historic Nubian civilizations.
-
D.
maritime archaeological site
A maritime archaeological site is a submerged or coastal location containing physical remains, artifacts, or environmental evidence that reveal past human activities related to seafaring, trade, or coastal life.
-
E.
Portuguese trading post
A Portuguese trading post is a fortified coastal or riverside settlement established by Portugal during the Age of Exploration to control trade routes, facilitate commerce, and project imperial influence.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:09 p.m.