Triple
T12847962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Khumalo |
E307232
|
entity |
| Predicate | clan |
P1915
|
FINISHED |
| Object | Khumalo |
E1000046
|
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: Khumalo | Statement: [House of Khumalo, clan, Khumalo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khumalo Context triple: [House of Khumalo, clan, Khumalo]
-
A.
Khumalo
chosen
Khumalo is a common Southern African surname associated with notable figures in arts, politics, and public life, particularly in South Africa and Zimbabwe.
-
B.
Mokoena
Mokoena is a common Southern African surname of Sotho-Tswana origin borne by various notable figures in politics, sports, and the arts.
-
C.
Thokozani
Thokozani is a given name most notably borne by Zimbabwean politician Thokozani Khupe.
-
D.
Makgoba
Makgoba is a South African surname most prominently associated with Thabo Makgoba, the Anglican Archbishop of Cape Town.
-
E.
Khupe
Khupe is a surname most prominently associated with Thokozani Khupe, a Zimbabwean politician and former deputy prime minister.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9701fe684819084582d1b4c809429 |
completed | April 10, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c0e393fc8190812380a3e41778bf |
completed | May 3, 2026, 3:28 a.m. |
Created at: April 9, 2026, 5:36 p.m.