Triple
T4999781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelenna |
E112340
|
entity |
| Predicate | electoralWardFor |
P61409
|
FINISHED |
| Object | local government elections |
—
|
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: local government elections | Statement: [Pelenna, electoralWardFor, local government elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralWardFor Context triple: [Pelenna, electoralWardFor, local government elections]
-
A.
localElectoralArea
Indicates a relationship where a geographic or administrative region is designated as a specific local electoral area for voting or representation purposes.
-
B.
containsWard
Indicates that one entity includes, encompasses, or has within it a ward (such as a district, division, or dependent person) as part of its scope or responsibility.
-
C.
placeOfElection
Indicates the location where an election or voting event took place.
-
D.
hasNeighbouringWard
Indicates that one ward is directly adjacent to or borders another ward geographically.
-
E.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
- F. None of above. chosen
Provenance (4 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd74713fc88190916c2b04cd2e677e |
completed | March 20, 2026, 4:23 p.m. |
Created at: March 20, 2026, 1:34 p.m.