Triple
T106004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Diet |
E2137
|
entity |
| Predicate | votingSystemLowerHouse |
P1307
|
FINISHED |
| Object | parallel voting |
—
|
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: parallel voting | Statement: [National Diet, votingSystemLowerHouse, parallel voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSystemLowerHouse Context triple: [National Diet, votingSystemLowerHouse, parallel voting]
-
A.
hasVotingSystemLowerHouse
chosen
Indicates that a political entity’s lower legislative chamber uses a specified voting or electoral system.
-
B.
lowerHouse
Indicates that one entity functions as the lower chamber of a bicameral legislature in relation to a given political body or system.
-
C.
electoralBody
Indicates that an entity functions as an official body responsible for overseeing, administering, or making decisions related to elections for another entity.
-
D.
votingUnit
Indicates a relationship where an entity functions as a unit or body that casts votes or participates in a voting process.
-
E.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a256ec650c8190bee2067e37065527 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563d33788190999d471b486d5603 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.