Triple

T22470949
Position Surface form Disambiguated ID Type / Status
Subject Lepelle-Nkumpi Local Municipality E555496 entity
Predicate governs P760 FINISHED
Object Lebowakgomo 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: Lebowakgomo | Statement: [Lepelle-Nkumpi Local Municipality, governs, Lebowakgomo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lebowakgomo
Context triple: [Lepelle-Nkumpi Local Municipality, governs, Lebowakgomo]
  • A. Lebowakgomo chosen
    Lebowakgomo is a township in the Limpopo province of South Africa that serves as an administrative and residential center for the surrounding region.
  • B. Lobamba
    Lobamba is the traditional and legislative capital of Eswatini, serving as the seat of the Swazi monarchy and key national institutions.
  • C. Thohoyandou
    Thohoyandou is a town in South Africa’s Limpopo province that serves as an administrative, commercial, and educational hub for the surrounding region.
  • D. Luanshya
    Luanshya is a mining town in Zambia known for its copper production and role in the country’s Copperbelt region.
  • E. Buhe
    Buhe was a Chinese politician of Mongol ethnicity who served in various regional leadership roles, including as chairman of the Inner Mongolia Autonomous Region.
  • 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_69e11e52c2048190952dc5df209b9bed completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15bdf6dfc8190aa8dc80ad92a9267 completed April 29, 2026, 1:16 a.m.
Created at: April 16, 2026, 8:48 p.m.