Triple
T21204194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Politics of Estonia |
E522534
|
entity |
| Predicate | votingSystemParliament |
P39112
|
FINISHED |
| Object | open list proportional representation |
—
|
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: open list proportional representation | Statement: [Politics of Estonia, votingSystemParliament, open list proportional representation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSystemParliament Context triple: [Politics of Estonia, votingSystemParliament, open list proportional representation]
-
A.
votingSystemChamber
Indicates the specific legislative chamber in which a given voting system is used or applies.
-
B.
votingSystemLokSabha
Indicates the type or method of voting system used for elections to the Lok Sabha.
-
C.
electoralSystemForLegislature
chosen
Indicates the type of electoral system used to choose members of a particular legislature.
-
D.
votingSystemUpperHouse
Indicates a relationship where a specified voting system is used to elect or constitute the members of an upper legislative house.
-
E.
votingSystemInSecondChamber
Indicates the type or method of voting used within a legislature’s second (upper) chamber.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7343367308190b1b772d3c8e25dcb |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:19 p.m.