Triple
T37858521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Calabar polity |
E944258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | West African trading center |
C61632
|
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: West African trading center Context triple: [Old Calabar polity, instanceOf, West African trading center]
-
A.
trans-Saharan trade hub
A trans-Saharan trade hub is a strategically located settlement or city that facilitates the exchange of goods, cultures, and ideas between sub-Saharan Africa and North Africa across the Sahara Desert.
-
B.
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.
-
C.
West African empire
A West African empire is a large, centralized political and economic state that historically controlled extensive territories in West Africa through complex governance, trade networks, military power, and cultural influence.
-
D.
medieval West African kingdom
A medieval West African kingdom is a centralized political and cultural entity that flourished between roughly the 8th and 16th centuries, characterized by hierarchical governance, control of trans-Saharan trade routes, and rich traditions in art, religion, and scholarship.
-
E.
historical trade center
chosen
A historical trade center is a geographically strategic hub where merchants, goods, cultures, and ideas converged over time, driving regional economic activity and cross-cultural exchange.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.