Triple
T31447845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taghaza |
E802237
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trans-Saharan trade hub |
C60998
|
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: trans-Saharan trade hub Context triple: [Taghaza, instanceOf, trans-Saharan trade hub]
-
A.
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.
-
B.
ancient trade route
An ancient trade route is a historically established pathway or network used for the long-distance exchange of goods, ideas, cultures, and technologies between regions and civilizations.
-
C.
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.
-
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.
colonial-era trade corridor
A colonial-era trade corridor is a strategically established route or network used during colonial times to transport goods, people, and resources between colonies and imperial centers, shaping economic patterns and cultural exchanges.
- F. None of above. chosen
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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:10 p.m.