Triple
T5615008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhukhune District Municipality |
E147454
|
entity |
| Predicate | municipalCode |
P3943
|
FINISHED |
| Object | DC47 |
E534712
|
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: DC47 | Statement: [Sekhukhune District Municipality, municipalCode, DC47]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DC47 Context triple: [Sekhukhune District Municipality, municipalCode, DC47]
-
A.
DC47
chosen
DC47 is the ISO code designating South Africa’s Sekhukhune District Municipality in Limpopo Province.
-
B.
DC35
DC35 is the official municipal code designating the Capricorn District Municipality in South Africa’s Limpopo province.
-
C.
DC42
DC42 is the official municipal code assigned to the Sedibeng District Municipality in South Africa’s local government system.
-
D.
Siemens Charger
The Siemens Charger is a family of modern diesel-electric passenger locomotives widely used across North America for intercity and commuter rail services.
-
E.
Schneider
Schneider is a German-origin surname commonly borne by people of German-speaking or Central European descent.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02123fa9081909086c9cce3f3e907 |
completed | March 22, 2026, 5:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a0ab9cc8190a01c5309e6cfc598 |
completed | March 22, 2026, 9:07 p.m. |
Created at: March 22, 2026, 3:39 p.m.