Triple

T11930359
Position Surface form Disambiguated ID Type / Status
Subject Vaal River industrial corridor E283894 entity
Predicate includesTown P847 FINISHED
Object Sasolburg E135668 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: Sasolburg | Statement: [Vaal River industrial corridor, includesTown, Sasolburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sasolburg
Context triple: [Vaal River industrial corridor, includesTown, Sasolburg]
  • A. Sasolburg chosen
    Sasolburg is an industrial town in South Africa’s Free State province, known primarily for its large petrochemical complex and proximity to the Vaal River.
  • B. Rustenburg
    Rustenburg is a city in South Africa’s North West Province known for its mining industry and as one of the venues for the 2010 FIFA World Cup.
  • C. Bothasig
    Bothasig is a residential suburb in the northern part of Cape Town, South Africa.
  • D. Colesberg
    Colesberg is a small historic town in South Africa’s Northern Cape, known as a key stopover on the N1 highway and a gateway to the semi-arid Karoo region.
  • E. Groblersdal
    Groblersdal is a town in South Africa’s Limpopo province known as an important agricultural center, particularly for irrigation-based farming.
  • 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_69d6ab2ce9c48190b5d39511b524f666 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90303a9a88190a4044e6310ba9b4b completed April 10, 2026, 2:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4406ee910819093c72738bfe3f92c completed May 1, 2026, 5:55 a.m.
Created at: April 8, 2026, 9:45 p.m.