Triple
T35029276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2026 Scottish Parliament election |
E1010429
|
entity |
| Predicate | ballotTypes |
P78405
|
FINISHED |
| Object | constituency ballot |
—
|
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: constituency ballot | Statement: [2026 Scottish Parliament election, ballotTypes, constituency ballot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballotTypes Context triple: [2026 Scottish Parliament election, ballotTypes, constituency ballot]
-
A.
ballotStructure
Indicates how options, candidates, or choices are organized and presented on a ballot for selection.
-
B.
hasBallotType
chosen
Indicates that an election, ballot, or voting process uses or is associated with a specific type or format of ballot.
-
C.
typeOfVoting
Indicates the specific method or system by which a vote is cast or recorded in a decision-making process.
-
D.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
E.
ballotUnitUsed
Indicates that a particular ballot unit was utilized in the conduct of an election or voting process.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.