Triple

T35223861
Position Surface form Disambiguated ID Type / Status
Subject Nyamande Lobengula E1017034 entity
Predicate instanceOf P0 FINISHED
Object member of Khumalo dynasty C11835 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: member of Khumalo dynasty
Context triple: [Nyamande Lobengula, instanceOf, member of Khumalo dynasty]
  • A. Ndebele king chosen
    An Ndebele king is the hereditary monarch and supreme traditional leader of the Ndebele people, responsible for upholding cultural customs, political authority, and social cohesion within the kingdom.
  • B. Mthethwa ruler
    A Mthethwa ruler is a sovereign leader of the Mthethwa polity, responsible for governing its people, managing political and military affairs, and upholding the customs and authority of the Mthethwa dynasty.
  • C. South African royal
    A South African royal is a member of a traditional monarchy or chieftaincy in South Africa who holds hereditary authority, cultural leadership, and ceremonial responsibilities within a specific indigenous community or kingdom.
  • D. Bapedi monarch
    A Bapedi monarch is the hereditary sovereign leader of the Bapedi people, embodying their political authority, cultural identity, and traditional customs within the Bapedi kingdom.
  • E. Zulu prince
    A Zulu prince is a male member of the Zulu royal family, traditionally positioned within the kingdom’s hereditary leadership structure and associated with cultural, political, and ceremonial roles.
  • 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_69f76de072908190ab65038a8a7b6a79 completed May 3, 2026, 3:46 p.m.
Created at: May 3, 2026, 4:02 p.m.