Triple
T34745006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1936 Kansas gubernatorial election |
E1001611
|
entity |
| Predicate | hasBallotScope |
P77868
|
FINISHED |
| Object | statewide |
—
|
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: statewide | Statement: [1936 Kansas gubernatorial election, hasBallotScope, statewide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBallotScope Context triple: [1936 Kansas gubernatorial election, hasBallotScope, statewide]
-
A.
hasBallotType
Indicates that an election, ballot, or voting process uses or is associated with a specific type or format of ballot.
-
B.
hasBallotAccessFor
Indicates that an entity is permitted or qualified to appear on the ballot for a particular election or jurisdiction.
-
C.
votingScope
chosen
Indicates the range or domain within which a voting action or decision is valid, applicable, or authorized.
-
D.
ballotOf
Indicates that one entity is the ballot associated with, used by, or belonging to another entity (such as a voter, election, or voting event).
-
E.
hasBallotLine
Indicates that an entity (typically a candidate or party) appears as a selectable option on a specific ballot line in an election.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 3:59 p.m.