Triple

T10909854
Position Surface form Disambiguated ID Type / Status
Subject FVHA E257666 entity
Predicate servesMetropolitanArea P82 FINISHED
Object Harare metropolitan area E252219 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 metropolitan area | Statement: [FVHA, servesMetropolitanArea, Harare metropolitan area]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harare metropolitan area
Context triple: [FVHA, servesMetropolitanArea, Harare metropolitan area]
  • A. Harare
    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. Chitungwiza
    Chitungwiza is a large high-density dormitory town in Zimbabwe situated just south of Harare, known for its rapid urban growth and vibrant informal economy.
  • D. Harare Province chosen
    Harare Province is the metropolitan province in Zimbabwe that encompasses the capital city, Harare, and its surrounding urban areas.
  • E. Bulawayo
    Bulawayo is Zimbabwe’s second-largest city and a major industrial, cultural, and transport hub in the southwestern part 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_69d6aa864ed88190818280ab6791d065 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d77068e5488190bbc881ebf51d6b2e completed April 9, 2026, 9:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69e216da42a0819095def6a691abf107 completed April 17, 2026, 11:17 a.m.
Created at: April 8, 2026, 9:22 p.m.