Triple
T1660521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | d’Hondt method |
E35893
|
entity |
| Predicate | allocatesSeatsBy |
P9552
|
FINISHED |
| Object | selecting highest quotients across parties |
—
|
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: selecting highest quotients across parties | Statement: [d’Hondt method, allocatesSeatsBy, selecting highest quotients across parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocatesSeatsBy Context triple: [d’Hondt method, allocatesSeatsBy, selecting highest quotients across parties]
-
A.
seatsForParty
Indicates that a seating arrangement or capacity is designated to accommodate a specific party or group.
-
B.
seatNotationSystem
Indicates the system or convention used to label, number, or otherwise denote seats within a venue or vehicle.
-
C.
seatingConfiguration
Indicates how seats are arranged or organized relative to each other in a given context.
-
D.
hasReservedSeats
Indicates that specific seats have been set aside or allocated in advance for a particular entity or purpose.
-
E.
seatSelectionPolicy
chosen
Indicates the rules or constraints governing how seats are chosen or assigned in a given context.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa994f92b0819084ee2f6a672334b9 |
completed | March 6, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69a907d2475c8190b7ec7dccd3335eb1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.