Triple

T378244
Position Surface form Disambiguated ID Type / Status
Subject National Assembly of Zimbabwe E8617 entity
Predicate meetsIn 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: [National Assembly of Zimbabwe, meetsIn, Harare]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harare
Context triple: [National Assembly of Zimbabwe, meetsIn, 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. Lusaka, Zambia
    Lusaka, Zambia is the capital and largest city of Zambia, serving as the country’s political, economic, and cultural center.
  • 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_69a2e7f47dd08190a4e294ccbbe46cd4 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec2974988190a1d6316cbb5159c8 completed Feb. 28, 2026, 1:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3f4ded68c8190b6951c03fd75c404 completed March 1, 2026, 8:12 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.