Triple
T14057917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sosso state |
E338266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval West African kingdom |
C34026
|
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: medieval West African kingdom Context triple: [Sosso state, instanceOf, medieval West African kingdom]
-
A.
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.
-
B.
Hausa city-state
A Hausa city-state is an autonomous urban-centered political entity historically found in the Hausa-speaking regions of West Africa, characterized by its own ruler, bureaucracy, economy, and surrounding rural hinterland.
-
C.
Christian Nubian state
A Christian Nubian state is a medieval kingdom in the Nubian region of the Nile Valley whose political, social, and cultural life was organized around Christian institutions, beliefs, and alliances.
-
D.
Yoruba city-state
A Yoruba city-state is an autonomous urban-centered political entity historically found in southwestern Nigeria and neighboring regions, typically organized around a sacred king (oba), a complex hierarchy of chiefs, and vibrant economic, religious, and artistic institutions.
-
E.
Berber kingdom
A Berber kingdom is a historically or contemporarily Berber-ruled political entity in North Africa or the Sahara, characterized by Berber language, culture, and social structures as central to its governance and identity.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.