Triple

T12847984
Position Surface form Disambiguated ID Type / Status
Subject House of Khumalo E307232 entity
Predicate traditionalCapital P20966 FINISHED
Object Bulawayo (royal town) E9766 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: Bulawayo (royal town) | Statement: [House of Khumalo, traditionalCapital, Bulawayo (royal town)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bulawayo (royal town)
Context triple: [House of Khumalo, traditionalCapital, Bulawayo (royal town)]
  • A. Bulawayo chosen
    Bulawayo is Zimbabwe’s second-largest city and a major industrial, cultural, and transport hub in the southwestern part of the country.
  • B. Marondera
    Marondera is a town in eastern Zimbabwe known as an agricultural and educational center within the Mashonaland region.
  • C. Chegutu
    Chegutu is a town in central northern Zimbabwe known for its agricultural activities and gold mining.
  • D. Chinhoyi
    Chinhoyi is a town in northern Zimbabwe known as an administrative center and for the nearby Chinhoyi Caves.
  • E. Manzini
    Manzini is a major city in Eswatini that serves as an important commercial and transport hub of the country.
  • 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_69d7bdf5e7cc8190be357278bc5ba3bb completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9701fe684819084582d1b4c809429 completed April 10, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6af511b4c8190bee09c938b2a7a12 completed May 3, 2026, 2:13 a.m.
Created at: April 9, 2026, 5:36 p.m.