Triple
T16463408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oliy Majlis of Uzbekistan |
E399866
|
entity |
| Predicate | votingSystemUsedInLowerHouse |
P1307
|
FINISHED |
| Object | mixed electoral system |
—
|
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: mixed electoral system | Statement: [Oliy Majlis of Uzbekistan, votingSystemUsedInLowerHouse, mixed electoral system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSystemUsedInLowerHouse Context triple: [Oliy Majlis of Uzbekistan, votingSystemUsedInLowerHouse, mixed electoral system]
-
A.
hasVotingSystemLowerHouse
chosen
Indicates that a political entity’s lower legislative chamber uses a specified voting or electoral system.
-
B.
lowerHouseElectedBy
Indicates that the members of the lower house of a legislature are chosen through a specified method or by a particular group of voters or body.
-
C.
electoralSystemForLegislature
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.
typeOfVoting
Indicates the specific method or system by which a vote is cast or recorded in a decision-making 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d83687081908450657e1da6f6af |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.