Triple
T35815882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daudi Chwa II of Buganda |
E1035356
|
entity |
| Predicate | successorAsKabaka |
P201921
|
FINISHED |
| Object | Mutesa II of Buganda |
—
|
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: Mutesa II of Buganda | Statement: [Daudi Chwa II of Buganda, successorAsKabaka, Mutesa II of Buganda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsKabaka Context triple: [Daudi Chwa II of Buganda, successorAsKabaka, Mutesa II of Buganda]
-
A.
successorAsKingOfKings
Indicates that one entity directly follows another in holding the title or role of King of Kings.
-
B.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
C.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
D.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
-
E.
successorAsValideSultan
Indicates that one entity became the next legitimate or officially recognized sultan after another entity.
- F. None of above. chosen
Provenance (4 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_6a0031ec758c81908a3877bc19ce2701 |
completed | May 10, 2026, 7:21 a.m. |
Created at: May 3, 2026, 4:06 p.m.