Triple

T23253299
Position Surface form Disambiguated ID Type / Status
Subject Malamulele E581794 entity
Predicate near P350 FINISHED
Object Thohoyandou 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: Thohoyandou | Statement: [Malamulele, near, Thohoyandou]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thohoyandou
Context triple: [Malamulele, near, Thohoyandou]
  • A. Thohoyandou chosen
    Thohoyandou is a town in South Africa’s Limpopo province that serves as an administrative, commercial, and educational hub for the surrounding region.
  • B. Lebowakgomo
    Lebowakgomo is a township in the Limpopo province of South Africa that serves as an administrative and residential center for the surrounding region.
  • C. Luanshya
    Luanshya is a mining town in Zambia known for its copper production and role in the country’s Copperbelt region.
  • D. Masandawana
    Masandawana is the popular nickname of South African football club Mamelodi Sundowns F.C., one of the country’s most successful and widely supported teams.
  • E. Mochudi
    Mochudi is a large village in southeastern Botswana that serves as a cultural and historical center of the Bakgatla people.
  • 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_69e24606b17c81908aba1a4911c8a8ba completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f193f840dc819098e52272abefe616 completed April 29, 2026, 5:15 a.m.
Created at: April 17, 2026, 4:11 p.m.