Triple
T28985255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish general elections |
E734661
|
entity |
| Predicate | simultaneousElections |
P112700
|
FINISHED |
| Object | county council elections |
—
|
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: county council elections | Statement: [Swedish general elections, simultaneousElections, county council elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: simultaneousElections Context triple: [Swedish general elections, simultaneousElections, county council elections]
-
A.
electionsHeldOnSameDayAs
chosen
Indicates that two elections took place on the exact same calendar day.
-
B.
hasGeneralElections
Indicates that general elections are held or occur in relation to the specified entity.
-
C.
legislatureElection
Indicates that an election is held to choose representatives for a legislative body or parliament.
-
D.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
E.
electionsScheduledFor
Indicates that a specific election is planned or set to occur at a particular time or for a particular entity.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f78c4d08190b68ee2b2fed19fff |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:13 a.m.