Triple
T24641528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makhado Local Municipality |
E609977
|
entity |
| Predicate | usesMunicipalCouncilSystem |
P86873
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Makhado Local Municipality, usesMunicipalCouncilSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMunicipalCouncilSystem Context triple: [Makhado Local Municipality, usesMunicipalCouncilSystem, yes]
-
A.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
B.
usesMunicipalGovernmentAct
Indicates that an entity operates under, applies, or is governed by the provisions of a Municipal Government Act.
-
C.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
D.
hasLocalGovernmentSystem
chosen
Indicates that an entity possesses or operates under a particular system or structure of local government.
-
E.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f40db2b5e08190bb55d02a4ceba306 |
completed | May 1, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d2b20881908dcc3b15cbe3e5b0 |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:33 a.m.