Triple
T2808882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaal Triangle |
E54119
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Vanderbijlpark |
E58237
|
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: Vanderbijlpark | Statement: [Vaal Triangle, hasCity, Vanderbijlpark]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vanderbijlpark Context triple: [Vaal Triangle, hasCity, 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.
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.
-
D.
Ermelo
Ermelo is a key agricultural and transport hub town located in South Africa’s Mpumalanga province.
-
E.
Boksburg
Boksburg is an industrial and residential city on the East Rand in Gauteng, South Africa, historically known for its coal mining and proximity to Johannesburg.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde3165b48190a43be5e6ad23deca |
completed | March 7, 2026, 8:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce97c3008190a966441d719d1d1c |
completed | March 10, 2026, 7:56 a.m. |
Created at: March 6, 2026, 9:59 p.m.