Triple
T33662742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highland constituencies |
E862395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of UK parliamentary constituencies |
C29891
|
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: group of UK parliamentary constituencies Context triple: [Highland constituencies, instanceOf, group of UK parliamentary constituencies]
-
A.
group of parliamentary constituencies
chosen
A group of parliamentary constituencies is a collection of electoral districts that are treated together for purposes such as representation, analysis, or administrative organization within a parliamentary system.
-
B.
former UK parliamentary constituency
A former UK parliamentary constituency is a geographic electoral area in the United Kingdom that once elected a Member of Parliament to the House of Commons but has since been abolished or replaced due to boundary changes or legislative reforms.
-
C.
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.
-
D.
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.
-
E.
parliamentary constituency category
A parliamentary constituency category is a classification grouping electoral districts that share common characteristics, such as geography, representation type, or legislative system, for organizational and analytical purposes.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.