Triple
T28349712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Scottish Parliament election |
E718058
|
entity |
| Predicate | regionalVote |
P192132
|
FINISHED |
| Object | party list |
—
|
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: party list | Statement: [2011 Scottish Parliament election, regionalVote, party list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalVote Context triple: [2011 Scottish Parliament election, regionalVote, party list]
-
A.
votingRegion
Indicates the geographic or administrative area in which an entity is eligible or authorized to vote.
-
B.
votingUnit
Indicates a relationship where an entity functions as a unit or body that casts votes or participates in a voting process.
-
C.
alsoInElectoralRegion
Indicates that an entity is located within, or belongs to, the same electoral region as another entity.
-
D.
regionWithStrongBlocSupport
Indicates that a geographic region exhibits notably high or concentrated support for a particular political bloc or alliance.
-
E.
partOfElectoralRegionSystem
Indicates that an electoral region belongs to, or is included within, a specific overarching electoral region system or framework.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 28, 2026, 12:45 a.m.