Triple
T6811682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch provincial elections |
E156647
|
entity |
| Predicate | votingIsCompulsory |
P31217
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Dutch provincial elections, votingIsCompulsory, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingIsCompulsory Context triple: [Dutch provincial elections, votingIsCompulsory, no]
-
A.
votingObligation
chosen
Indicates that an entity is required or expected to participate in a voting process, typically by law, rule, or formal duty.
-
B.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
C.
legalStatusOfElectors
Indicates the legal standing, rights, and recognition granted to electors under applicable laws or regulations.
-
D.
usesElectoralRight
Indicates that an entity exercises its electoral rights, such as voting or otherwise participating in an electoral process.
-
E.
politicalRequirement
Indicates that one entity imposes or must satisfy a political condition, qualification, or constraint in relation to another entity or 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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.