Triple

T11571367
Position Surface form Disambiguated ID Type / Status
Subject National Railways of Zimbabwe E274393 entity
Predicate servesCity P82 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 Railways of Zimbabwe, servesCity, Harare]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harare
Context triple: [National Railways of Zimbabwe, servesCity, Harare]
  • A. Harare chosen
    Harare is the largest city and main economic, political, and cultural center of Zimbabwe.
  • B. 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.
  • C. Masvingo
    Masvingo is one of Zimbabwe’s oldest urban centers, located in the country’s southeastern region near the Great Zimbabwe ruins.
  • D. Bulawayo
    Bulawayo is Zimbabwe’s second-largest city and a major industrial, cultural, and transport hub in the southwestern part of the country.
  • E. Marondera
    Marondera is a town in eastern Zimbabwe known as an agricultural and educational center within the Mashonaland region.
  • 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_69d6aae5ac3c81908d2b0a3a665665b2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d88dd6913881908becf188c0a7a275 completed April 10, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69e6e8eface48190a2ed3275191b01ea completed April 21, 2026, 3:03 a.m.
Created at: April 8, 2026, 9:38 p.m.