Triple
T23852786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pollokshields |
E592217
|
entity |
| Predicate | cityCouncilWard |
P76280
|
FINISHED |
| Object | Pollokshields ward |
—
|
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: Pollokshields ward | Statement: [Pollokshields, cityCouncilWard, Pollokshields ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCouncilWard Context triple: [Pollokshields, cityCouncilWard, Pollokshields ward]
-
A.
electoralWardFor
Indicates that one entity serves as the electoral ward or voting district in which another entity (such as a place or address) is located or represented.
-
B.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
-
C.
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.
-
D.
locatedInCityWard
chosen
Indicates that one entity is situated within the administrative boundaries of a specific city ward.
-
E.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c9887e5c819089437769acf684c4 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.