Triple
T31099536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubaid dynasty |
E792630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | North African dynasty |
C9262
|
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: North African dynasty Context triple: [Jubaid dynasty, instanceOf, North African dynasty]
-
A.
Berber Muslim dynasty
chosen
A Berber Muslim dynasty is a ruling family or lineage of Berber origin that governed a region within the Islamic world, combining indigenous Amazigh (Berber) cultural elements with Islamic political and religious authority.
-
B.
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.
-
C.
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.
-
D.
Vandal dynasty
The Vandal dynasty was a Germanic royal lineage that ruled a North African kingdom centered on Carthage from the early 5th to mid-6th century CE, known for its maritime power and conflicts with the Western Roman Empire and Byzantium.
-
E.
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.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:03 p.m.