Triple

T2536889
Position Surface form Disambiguated ID Type / Status
Subject Regional Service Centre Entebbe E56290 entity
Predicate city P40 FINISHED
Object Entebbe E44536 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: Entebbe | Statement: [Regional Service Centre Entebbe, city, Entebbe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Entebbe
Context triple: [Regional Service Centre Entebbe, city, Entebbe]
  • A. Entebbe chosen
    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.
  • B. Kampala
    Kampala is the capital and largest city of Uganda, serving as the country’s political, economic, and cultural center.
  • C. Mukono
    Mukono is a town in central Uganda that serves as the administrative and commercial center of Mukono District, located just east of the capital Kampala.
  • D. Kalangala
    Kalangala is a town on Uganda’s Ssese Islands in Lake Victoria, serving as the administrative and commercial center of Kalangala District.
  • E. Runyankole
    Runyankole is a Bantu language spoken primarily by the Banyankole people in southwestern Uganda.
  • 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_69ab4a49b6508190bc467fbef4bac334 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd297e9a881909e592187a78eacaa completed March 7, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69af5cf858cc81908d6a7ef5315119aa completed March 9, 2026, 11:51 p.m.
Created at: March 6, 2026, 9:47 p.m.