Triple

T11793447
Position Surface form Disambiguated ID Type / Status
Subject Oluganda E280444 entity
Predicate region P40 FINISHED
Object Buganda E203300 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: Buganda | Statement: [Oluganda, region, Buganda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buganda
Context triple: [Oluganda, region, Buganda]
  • A. Buganda chosen
    Buganda is a traditional Bantu kingdom in central Uganda that is the country’s most populous and historically influential region.
  • B. Nakasongola
    Nakasongola is a town in central Uganda that serves as an administrative and commercial center for the surrounding rural district.
  • C. Kanyaga
    "Kanyaga" is a popular Tanzanian Bongo Flava hit song by Diamond Platnumz known for its energetic beat and danceable style.
  • D. Bindura
    Bindura is a town in northern Zimbabwe that serves as the administrative and commercial center of the surrounding mining and agricultural region.
  • E. Bagamoyo
    Bagamoyo is a historic coastal town in present-day Tanzania that served as a major 19th-century East African trade and colonial center, including as an early administrative hub for German rule.
  • 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_69d6ab258b808190b1735835c841e3a4 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5a082d08190a42541396a06ed98 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f09115c66c8190b0a3e775bdf575c1 completed April 28, 2026, 10:51 a.m.
Created at: April 8, 2026, 9:42 p.m.