Triple

T15945135
Position Surface form Disambiguated ID Type / Status
Subject Sheko E386664 entity
Predicate glottologName P6521 FINISHED
Object Sheko E386664 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: Sheko | Statement: [Sheko, glottologName, Sheko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sheko
Context triple: [Sheko, glottologName, Sheko]
  • A. Sheko chosen
    Sheko is an Omotic language spoken primarily in southwestern Ethiopia by the Sheko people.
  • 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. Nyamande Lobengula
    Nyamande Lobengula was a Ndebele royal figure and son of King Lobengula, associated with the Khumalo ruling dynasty in what is now Zimbabwe.
  • 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. Sekhukhune I
    Sekhukhune I was a 19th-century king of the Bapedi (Pedi) people in present-day South Africa, known for his resistance against Boer and British colonial expansion.
  • 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_69d86da882448190a82ea962fe343b79 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156d0d55c8190af59ff169e8add78 completed April 16, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffbe76df6481909f8246099faa377a completed May 9, 2026, 11:08 p.m.
Created at: April 10, 2026, 4:53 a.m.