Triple

T13593640
Position Surface form Disambiguated ID Type / Status
Subject Mutare City Hall E324757 entity
Predicate governs P760 FINISHED
Object City of Mutare E10728 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: City of Mutare | Statement: [Mutare City Hall, governs, City of Mutare]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Mutare
Context triple: [Mutare City Hall, governs, City of Mutare]
  • A. Mutare chosen
    Mutare is a major city in eastern Zimbabwe, serving as the capital of Manicaland Province and an important commercial and transport hub near the border with Mozambique.
  • B. Marondera
    Marondera is a town in eastern Zimbabwe known as an agricultural and educational center within the Mashonaland region.
  • C. Masvingo
    Masvingo is one of Zimbabwe’s oldest urban centers, located in the country’s southeastern region near the Great Zimbabwe ruins.
  • D. Chinhoyi
    Chinhoyi is a town in northern Zimbabwe known as an administrative center and for the nearby Chinhoyi Caves.
  • E. Chegutu
    Chegutu is a town in central northern Zimbabwe known for its agricultural activities and gold mining.
  • 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_69d80769eaf081909d82f44e484d6113 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb057f1c881909a3bb77c659a724a completed April 12, 2026, 2:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd08852a08190b9983e0c3058671a completed May 7, 2026, 5:48 p.m.
Created at: April 9, 2026, 9:49 p.m.