Triple

T199690
Position Surface form Disambiguated ID Type / Status
Subject Parliament of Zimbabwe E4074 entity
Predicate locatedIn P40 FINISHED
Object Harare E8616 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: Harare | Statement: [Parliament of Zimbabwe, locatedIn, Harare]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harare
Context triple: [Parliament of Zimbabwe, locatedIn, Harare]
  • A. Harare chosen
    Harare is the largest city and main economic, political, and cultural center of Zimbabwe.
  • B. Masvingo
    Masvingo is one of Zimbabwe’s oldest urban centers, located in the country’s southeastern region near the Great Zimbabwe ruins.
  • C. Bulawayo
    Bulawayo is Zimbabwe’s second-largest city and a major industrial, cultural, and transport hub in the southwestern part of the country.
  • D. Mutare
    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.
  • E. Pretoria, South Africa
    Pretoria, South Africa is one of the country’s three capital cities, serving as the administrative capital and a major center for government, education, and culture.
  • 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_69a254bca59881909a15e1496f1508c7 completed Feb. 28, 2026, 2:36 a.m.
NER Named-entity recognition batch_69a25bcc6dc88190b8c24b485588dfe4 completed Feb. 28, 2026, 3:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3232f11a08190ad532c68d9e8e2da completed Feb. 28, 2026, 5:17 p.m.
Created at: Feb. 28, 2026, 2:44 a.m.