Triple
T6671069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaka Smart |
E151730
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Shaka |
E125170
|
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: Shaka | Statement: [Shaka Smart, givenName, Shaka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shaka Context triple: [Shaka Smart, givenName, Shaka]
-
A.
King Shaka Zulu
chosen
King Shaka Zulu was the early 19th-century Zulu king and military innovator who forged the Zulu Kingdom into a powerful regional force in southern Africa.
-
B.
Shaka era
The Shaka era is a historical Indian calendar era that begins in 78 CE and is widely used for dating in traditional Hindu and official Indian calendars.
-
C.
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.
-
D.
Dingiswayo
Dingiswayo was a prominent early 19th-century Mthethwa king and military leader in southeastern Africa, known for mentoring and influencing the rise of Shaka Zulu.
-
E.
Sheko
Sheko is an Omotic language spoken primarily in southwestern Ethiopia by the Sheko people.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b0c9163c8190ad959172a8458619 |
completed | March 27, 2026, 4:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c723b8a5288190a2fb4d956f2dc385 |
completed | March 28, 2026, 12:41 a.m. |
Created at: March 27, 2026, 2:03 p.m.