Triple

T22049682
Position Surface form Disambiguated ID Type / Status
Subject Chevrons E544850 entity
Predicate homeGroundCity P13606 FINISHED
Object Bulawayo NE NERFINISHED

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: Bulawayo | Statement: [Chevrons, homeGroundCity, Bulawayo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bulawayo
Context triple: [Chevrons, homeGroundCity, Bulawayo]
  • A. Bulawayo chosen
    Bulawayo is Zimbabwe’s second-largest city and a major industrial, cultural, and transport hub in the southwestern part of the country.
  • B. Manzini
    Manzini is a major city in Eswatini that serves as an important commercial and transport hub of the country.
  • C. Amanzimtoti
    Amanzimtoti is a coastal resort town in KwaZulu-Natal, South Africa, known for its warm beaches and popularity as a holiday destination.
  • D. Okahandja
    Okahandja is a town in central Namibia known as a historical center of the Herero people and an important stop on the main route between Windhoek and the northern regions.
  • E. Witbank
    Witbank is a South African coal-mining city in Mpumalanga province, now officially known as Emalahleni.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f128323fb08190b9592fd08a96cba0 completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:26 p.m.