Triple
T23639907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois's 8th congressional district |
E583855
|
entity |
| Predicate | hasBallot |
P75786
|
FINISHED |
| Object | Illinois general elections |
—
|
NE NERFINISHED |
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: Illinois general elections | Statement: [Illinois's 8th congressional district, hasBallot, Illinois general elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBallot Context triple: [Illinois's 8th congressional district, hasBallot, Illinois general elections]
-
A.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
B.
hasBallotType
Indicates that an election, ballot, or voting process uses or is associated with a specific type or format of ballot.
-
C.
hasBallotLine
chosen
Indicates that an entity (typically a candidate or party) appears as a selectable option on a specific ballot line in an election.
-
D.
ballotStatus
Indicates the current state or outcome of a ballot within a voting or decision-making process.
-
E.
hasBallotAccessFor
Indicates that an entity is permitted or qualified to appear on the ballot for a particular election or jurisdiction.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2808d888190a2198f5efd25f2df |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.