Triple
T13865449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overberg District |
E333311
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bredasdorp |
E598775
|
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: Bredasdorp | Statement: [Overberg District, contains, Bredasdorp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bredasdorp Context triple: [Overberg District, contains, Bredasdorp]
-
A.
Bredasdorp
chosen
Bredasdorp is a small agricultural town in South Africa’s Western Cape, known as a gateway to the southern Overberg region and nearby coastal and nature attractions.
-
B.
Calitzdorp
Calitzdorp is a small town in South Africa’s Western Cape renowned for its port-style wines and scenic setting along Route 62.
-
C.
Blauwestad
Blauwestad is a modern lakeside residential and recreational area in the Dutch province of Groningen, developed around the artificial lake Oldambtmeer.
-
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.
Swellendam
Swellendam is a historic town in South Africa’s Western Cape, known for its Cape Dutch architecture and location near the Langeberg Mountains.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de05c30d9c81908217d41a3b4aaf85 |
completed | April 14, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea59d27bc81908ace0b7db9f57215 |
completed | May 9, 2026, 3:10 a.m. |
Created at: April 9, 2026, 10:14 p.m.