Triple
T8083870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish local government elections |
E188681
|
entity |
| Predicate | multiMemberWards |
P58846
|
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: [Scottish local government elections, multiMemberWards, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiMemberWards Context triple: [Scottish local government elections, multiMemberWards, yes]
-
A.
numberOfWards
Indicates the quantitative relationship specifying how many wards are associated with a given entity.
-
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.
hasNeighbouringWard
Indicates that one ward is directly adjacent to or borders another ward geographically.
-
D.
usesMultiMemberDistricts
chosen
Indicates that an electoral system or jurisdiction elects multiple representatives from the same district rather than just one.
-
E.
hasDistrictMembers
Indicates that a district includes or is composed of the specified members.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415e61ac81909e924aea69a7ff77 |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.