Triple
T36976108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DC39 |
E914702
|
entity |
| Predicate | previousNameOfDistrict |
P43887
|
FINISHED |
| Object | Bophirima District Municipality |
—
|
NE NERFINISHED |
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: Bophirima District Municipality | Statement: [DC39, previousNameOfDistrict, Bophirima District Municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNameOfDistrict Context triple: [DC39, previousNameOfDistrict, Bophirima District Municipality]
-
A.
formerNameOfDistrict
chosen
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
B.
formerNameOfProvince
Indicates that one name was previously used as the official name of a province before being replaced by another name.
-
C.
previousMunicipalityNameVariant
Indicates that an entity had a different municipality name in the past, specifying a former variant of its municipal designation.
-
D.
formerNameOfRegion
Indicates that one name was previously used for a region that is now known by a different name.
-
E.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
- F. None of above.
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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.