Triple
T18598830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vereeniging |
E454566
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Vanderbijlpark |
—
|
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: Vanderbijlpark | Statement: [Vereeniging, locatedNear, Vanderbijlpark]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vanderbijlpark Context triple: [Vereeniging, locatedNear, Vanderbijlpark]
-
A.
Vanderbijlpark
chosen
Vanderbijlpark is an industrial city in South Africa known for its large steel production facilities and location on the Vaal River.
-
B.
Roodepoort
Roodepoort is a suburban city on the western side of Johannesburg in South Africa, known for its residential areas, shopping centers, and proximity to the Witwatersrand hills.
-
C.
Durbanville
Durbanville is a suburban town in the northern outskirts of Cape Town, South Africa, known for its wine estates and residential character.
-
D.
Krugersdorp
Krugersdorp is a historic mining town in South Africa known for its gold deposits and location on the West Rand of the Gauteng province.
-
E.
Calitzdorp
Calitzdorp is a small town in South Africa’s Western Cape renowned for its port-style wines and scenic setting along Route 62.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474f1d548190b74408eabd396344 |
completed | April 19, 2026, 9:21 p.m. |
Created at: April 10, 2026, 11:45 a.m.