Triple
T22273703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mzilikazi |
E550545
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Inkosi |
—
|
NE NERFINISHED |
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: [Mzilikazi, title, Inkosi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inkosi Context triple: [Mzilikazi, title, 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.
Sikhuphe
Sikhuphe is a locality in Eswatini situated close to King Mswati III International Airport.
-
D.
Imolesi
Imolesi are the inhabitants or natives of the Italian city of Imola, located in the Emilia-Romagna region.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea547e4819098baf88f3c605242 |
completed | April 29, 2026, 12:19 a.m. |
Created at: April 16, 2026, 8:40 p.m.