Triple

T11596089
Position Surface form Disambiguated ID Type / Status
Subject Baganda E275004 entity
Predicate capitalRegionCity P3940 FINISHED
Object Kampala E40695 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: Kampala | Statement: [Baganda, capitalRegionCity, Kampala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kampala
Context triple: [Baganda, capitalRegionCity, Kampala]
  • A. Kampala chosen
    Kampala is the capital and largest city of Uganda, serving as the country’s political, economic, and cultural center.
  • B. Entebbe
    Entebbe is a town in central Uganda on a peninsula into Lake Victoria, known for its international airport and the site of the 1976 hostage-rescue operation.
  • C. Dodoma
    Dodoma is the political and administrative capital city of Tanzania, located in the country’s central region.
  • D. Lipa City
    Lipa City is a highly urbanized city in Batangas, Philippines, known as a commercial, educational, and religious center in the Calabarzon region.
  • E. Kabete
    Kabete is a prominent town in Kenya’s Central Region, situated within Kiambu County and known for its agricultural activity and proximity to Nairobi.
  • 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_69d6aae6b14c81908dc5a74bad7591f9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8946790d08190924d60bb4b523250 completed April 10, 2026, 6:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69e8a7b72c888190b069d0ebaebd31d9 completed April 22, 2026, 10:49 a.m.
Created at: April 8, 2026, 9:38 p.m.