Triple

T22752422
Position Surface form Disambiguated ID Type / Status
Subject Blyde River E562739 entity
Predicate near P350 FINISHED
Object Hoedspruit 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: Hoedspruit | Statement: [Blyde River, near, Hoedspruit]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoedspruit
Context triple: [Blyde River, near, Hoedspruit]
  • A. Hoedspruit chosen
    Hoedspruit is a small South African town near Kruger National Park, known as a gateway to wildlife reserves and scenic Lowveld attractions.
  • B. Sesheke
    Sesheke is a significant town in western Zambia’s Barotseland region, located near the Zambezi River and the border with Namibia.
  • C. Lebowakgomo
    Lebowakgomo is a township in the Limpopo province of South Africa that serves as an administrative and residential center for the surrounding region.
  • D. Nelspruit
    Nelspruit is a city in northeastern South Africa, now known as Mbombela, noted as a regional hub near Kruger National Park and for hosting matches during the 2010 FIFA World Cup.
  • E. Thohoyandou
    Thohoyandou is a town in South Africa’s Limpopo province that serves as an administrative, commercial, and educational hub for the surrounding 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_69e24551ec7881909a9c924dbea155f6 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f179baa85881909140f41f2428cc98 completed April 29, 2026, 3:23 a.m.
Created at: April 17, 2026, 3:24 p.m.