Triple
T35206556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buikwe District |
E1016551
|
entity |
| Predicate | belongsToTraditionalKingdom |
P20193
|
FINISHED |
| Object | Buganda Kingdom |
—
|
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: Buganda Kingdom | Statement: [Buikwe District, belongsToTraditionalKingdom, Buganda Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToTraditionalKingdom Context triple: [Buikwe District, belongsToTraditionalKingdom, Buganda Kingdom]
-
A.
recognizedAsKingdom
Indicates that an entity is formally acknowledged or classified as a kingdom within a given system or context.
-
B.
kingdomAssociatedWith
chosen
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
-
C.
eraOfHistoricalKingdom
Indicates the historical time period during which a particular kingdom existed or held prominence.
-
D.
overkingdomOf
Indicates that one kingdom holds overarching authority or sovereignty over another kingdom.
-
E.
hasTraditionalRulers
Indicates that one entity possesses or is governed by traditional rulers associated with it.
- F. None of above.
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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
Created at: May 3, 2026, 4:02 p.m.