Triple
T22476152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ndwandwe |
E555634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nguni polity |
C15760
|
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: Nguni polity Context triple: [Ndwandwe, instanceOf, Nguni polity]
-
A.
Moro polity
Moro polity refers to the traditional and historical systems of governance, authority, and social organization among the Muslim ethnolinguistic groups in the southern Philippines, particularly in Mindanao and the Sulu Archipelago.
-
B.
Tai polity
A Tai polity is a premodern socio-political entity formed by Tai-speaking peoples, typically organized around a muang (city-state) structure with a hierarchical ruler, tributary relations, and a mandala-style sphere of influence rather than fixed territorial borders.
-
C.
Bantu state
chosen
A Bantu state is a political entity historically or contemporarily governed by Bantu-speaking peoples, typically characterized by centralized authority, kinship-based social organization, and economies rooted in agriculture, herding, and regional trade.
-
D.
Shona-speaking polity
A Shona-speaking polity is a socio-political entity historically or contemporarily organized around communities whose primary language and cultural identity are Shona, typically located in present-day Zimbabwe and surrounding regions.
-
E.
Caucasian polity
A Caucasian polity is a political entity or state-like organization situated in or historically associated with the Caucasus region, encompassing its diverse ethnic, cultural, and geopolitical contexts.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:49 p.m.