Triple

T12908411
Position Surface form Disambiguated ID Type / Status
Subject Khumalo dynasty E308786 entity
Predicate titleOfRuler P10605 FINISHED
Object Inkosi E991366 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Inkosi | Statement: [Khumalo dynasty, titleOfRuler, Inkosi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inkosi
Context triple: [Khumalo dynasty, titleOfRuler, Inkosi]
  • A. Nkosi chosen
    Nkosi is a traditional royal title used for rulers and chiefs among the Mpondo people of South Africa.
  • B. Lobengula
    Lobengula was the second and last king of the Ndebele (Matabele) Kingdom in what is now Zimbabwe, known for his resistance to British colonial encroachment in the late 19th century.
  • C. Imolesi
    Imolesi are the inhabitants or natives of the Italian city of Imola, located in the Emilia-Romagna region.
  • D. Sekgoma II
    Sekgoma II was a Bangwato king of the Bechuanaland Protectorate (now Botswana) and a key traditional leader in the lineage that produced Botswana’s first president, Seretse Khama.
  • E. King Mzilikazi kaMashobane
    King Mzilikazi kaMashobane was a 19th-century Southern African monarch who founded the Ndebele (Matabele) nation and established a powerful kingdom in what is now western Zimbabwe.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69d7bdf92b588190acdf2a2291ac4590 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9719d4d1c8190a2c4f362e1772a73 completed April 10, 2026, 9:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6a5680d748190b8453793219bda8f completed May 3, 2026, 1:31 a.m.
Created at: April 9, 2026, 5:41 p.m.