Triple

T518855
Position Surface form Disambiguated ID Type / Status
Subject Uganda E10768 entity
Predicate capital P234 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: [Uganda, capital, Kampala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kampala
Context triple: [Uganda, capital, 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. Nairobi
    Nairobi is the capital and largest city of Kenya, serving as a major political, economic, and cultural hub in East Africa.
  • D. Kisumu
    Kisumu is a major Kenyan city on the shores of Lake Victoria, serving as a key commercial and transport hub in western Kenya.
  • E. Kinshasa
    Kinshasa is the largest city and political, economic, and cultural center of the Democratic Republic of the Congo, located along the Congo River in Central Africa.
  • 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_69a2e84a0d08819087e01863fcd9abf1 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f19ee6748190916603ef3a9e27f3 completed Feb. 28, 2026, 1:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4ab1dc61081908d7215b68f95b2ba completed March 1, 2026, 9:09 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.