Triple
T13654013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellville |
E326809
|
entity |
| Predicate | nearbyArea |
P2064
|
FINISHED |
| Object | Durbanville |
E555672
|
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: Durbanville | Statement: [Bellville, nearbyArea, Durbanville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Durbanville Context triple: [Bellville, nearbyArea, Durbanville]
-
A.
Durbanville
chosen
Durbanville is a suburban town in the northern outskirts of Cape Town, South Africa, known for its wine estates and residential character.
-
B.
Muizenberg
Muizenberg is a seaside suburb of Cape Town, South Africa, known for its popular surfing beach and colorful Victorian beach huts.
-
C.
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.
-
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.
Paarl
Paarl is a historic town in South Africa renowned for its wine estates, scenic granite rock formations, and role in the development of the Afrikaans language.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60ace048190a4b92310ba272bd1 |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd9498f8848190a170a3d41c9e3a76 |
completed | May 8, 2026, 7:45 a.m. |
Created at: April 9, 2026, 9:52 p.m.