Triple

T6684095
Position Surface form Disambiguated ID Type / Status
Subject Hwange E152056 entity
Predicate hasNearbyTown P3883 FINISHED
Object Lupane E152055 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: Lupane | Statement: [Hwange, hasNearbyTown, Lupane]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lupane
Context triple: [Hwange, hasNearbyTown, Lupane]
  • A. Lupane chosen
    Lupane is a small town in western Zimbabwe that serves as the administrative and commercial center of the Matabeleland North province.
  • B. Lomwe
    Lomwe is a Bantu language spoken primarily in Mozambique and Malawi by the Lomwe people.
  • C. Tshiphani
    Tshiphani is a regional dialect of the Tshivenda language spoken by Venda communities in parts of southern Africa.
  • D. Ndwandwe
    Ndwandwe was a powerful Nguni-speaking kingdom in southeastern Africa that rivaled the Mthethwa and played a major role in the early 19th-century upheavals that led to the rise of the Zulu state.
  • E. Makoni
    Makoni is a town in Zimbabwe’s Manicaland Province, known primarily as a local administrative and commercial center for the surrounding rural district.
  • 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_69c687f9977c819097e7f5ada4fe522e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b122df14819082068af37611b691 completed March 27, 2026, 4:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6f7ae8f388190a3c78c89b7293804 completed March 27, 2026, 9:33 p.m.
Created at: March 27, 2026, 2:04 p.m.