Triple
T25399252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish legislative election of 1985 |
E636373
|
entity |
| Predicate | voterChoice |
P35308
|
FINISHED |
| Object | limited to regime-approved list |
—
|
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: limited to regime-approved list | Statement: [Polish legislative election of 1985, voterChoice, limited to regime-approved list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voterChoice Context triple: [Polish legislative election of 1985, voterChoice, limited to regime-approved list]
-
A.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
-
B.
votePattern
Indicates a recurring way or tendency in how an entity casts votes across issues, candidates, or time.
-
C.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
D.
voteRecord
chosen
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
-
E.
voterApproval
Indicates that a voter has given consent, support, or positive endorsement to a proposal, candidate, or decision.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f8802c819085d55049bd94b075 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:50 p.m.