Triple
T14136088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copperbelt Province |
E350297
|
entity |
| Predicate | hasMiningTown |
P42429
|
FINISHED |
| Object | Mufulira |
E343322
|
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: Mufulira | Statement: [Copperbelt Province, hasMiningTown, Mufulira]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mufulira Context triple: [Copperbelt Province, hasMiningTown, Mufulira]
-
A.
Mufulira
chosen
Mufulira is a mining town in northern Zambia known for its large copper mines and role in the country's Copperbelt region.
-
B.
Gwanda
Gwanda is a small Zimbabwean town that serves as an administrative and commercial hub in the country’s arid south, known historically for cattle ranching and gold mining.
-
C.
Murehwa
Murehwa is a town and rural service center in northeastern Zimbabwe known for its agricultural activities and proximity to traditional Shona cultural sites.
-
D.
Nyabira
Nyabira is a small town in northern Zimbabwe located within Mashonaland West Province, serving as a local commercial and residential center.
-
E.
Lyantonde
Lyantonde is a town and district in central Uganda, situated within the traditional kingdom region of Buganda.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610fb86c81909eb26bf9c13696ca |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d043860819099526cbae1b1ef18 |
completed | May 8, 2026, 1:31 a.m. |
Created at: April 10, 2026, 12:18 a.m.