Triple
T8051196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow Southside |
E187677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish Parliamentary constituency |
C5906
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Scottish Parliamentary constituency Context triple: [Glasgow Southside, instanceOf, Scottish Parliamentary constituency]
-
A.
Scottish Parliament constituency
chosen
A Scottish Parliament constituency is a geographically defined electoral area in Scotland that elects one Member of the Scottish Parliament (MSP) to represent its residents in the devolved national legislature.
-
B.
Scottish Parliament electoral region
A Scottish Parliament electoral region is a large geographic area of Scotland used to elect additional members to the Scottish Parliament under the proportional representation element of its mixed-member electoral system.
-
C.
Westminster parliamentary constituency in Scotland
A Westminster parliamentary constituency in Scotland is a geographically defined electoral area within Scotland that elects one Member of Parliament (MP) to represent its residents in the UK House of Commons.
-
D.
UK parliamentary constituency
A UK parliamentary constituency is a geographically defined electoral area that elects one Member of Parliament (MP) to represent its residents in the House of Commons.
-
E.
UK Parliament constituency
A UK Parliament constituency is a geographically defined electoral area that elects a single Member of Parliament (MP) to represent its residents in the House of Commons.
- F. None of above.
Provenance (1 batch)
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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:24 p.m.