Triple
T34444515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port St Johns Local Municipality |
E884187
|
entity |
| Predicate | hasWardCouncillors |
P87204
|
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: [Port St Johns Local Municipality, hasWardCouncillors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWardCouncillors Context triple: [Port St Johns Local Municipality, hasWardCouncillors, yes]
-
A.
hasCouncillors
chosen
Indicates that an entity is associated with one or more councillors who serve or represent it in an official capacity.
-
B.
hasWardAssembly
Indicates that a specified ward is associated with a particular assembly or representative governing body.
-
C.
hasNumberOfCouncillors
Indicates the relationship that specifies how many councillors are associated with a given entity.
-
D.
hasMunicipalWards
Indicates that a municipality is divided into and associated with one or more municipal wards as its internal administrative units.
-
E.
hasElectoralWardStatus
Indicates that an entity holds the official status or designation of an electoral ward within an administrative or political system.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 2 a.m.