Triple
T38668552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Calabar |
E940520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former slave-trading port |
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: former slave-trading port Context triple: [Old Calabar, instanceOf, former slave-trading port]
-
A.
former port city
A former port city is an urban settlement that once functioned as a significant maritime trade hub but has since lost its port operations or primary seafaring role due to economic, environmental, or infrastructural changes.
-
B.
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.
-
C.
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.
-
D.
Swahili trading city
A Swahili trading city is a coastal urban center along the East African littoral that thrived as a hub of maritime commerce, cultural exchange, and Islamic influence, linking African hinterlands with the Indian Ocean world.
-
E.
maritime trading centre
A maritime trading centre is a coastal hub where goods, services, and information are exchanged via sea routes, integrating port infrastructure, commercial activities, and logistics networks to facilitate regional and international trade.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.