Triple
T20854600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bicameral Riksdag of Sweden |
E513446
|
entity |
| Predicate | votingSystemInFirstChamber |
P4892
|
FINISHED |
| Object | indirect election |
—
|
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: indirect election | Statement: [bicameral Riksdag of Sweden, votingSystemInFirstChamber, indirect election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSystemInFirstChamber Context triple: [bicameral Riksdag of Sweden, votingSystemInFirstChamber, indirect election]
-
A.
votingSystemChamber
Indicates the specific legislative chamber in which a given voting system is used or applies.
-
B.
hasVotingSystemLowerHouse
Indicates that a political entity’s lower legislative chamber uses a specified voting or electoral system.
-
C.
electoralSystemForLegislature
Indicates the type of electoral system used to choose members of a particular legislature.
-
D.
electedChamber
Indicates that an individual has been chosen through an election to serve as a member of a specific legislative chamber.
-
E.
votingSystemUpperHouse
chosen
Indicates a relationship where a specified voting system is used to elect or constitute the members of an upper legislative house.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a7113c819087994bcdfe643bc1 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.