Triple
T32609223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Blair |
E833606
|
entity |
| Predicate | hasCompulsoryVoting |
P31217
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Division of Blair, hasCompulsoryVoting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompulsoryVoting Context triple: [Division of Blair, hasCompulsoryVoting, yes]
-
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.
hasElectoralRight
Indicates that an entity possesses the legal right to participate in elections, typically by voting or standing as a candidate.
-
C.
requiredVoterRegistration
Indicates that an entity must be registered as a voter in order to participate in a specified voting-related activity or process.
-
D.
canVoteIn
Indicates that one entity has the legal right or eligibility to participate as a voter in an election or decision-making process associated with another entity.
-
E.
hasElectoralRoll
Indicates that an entity maintains, contains, or is associated with an official electoral roll listing eligible voters.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:05 a.m.