Triple
T34745005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1936 Kansas gubernatorial election |
E1001611
|
entity |
| Predicate | isPopularVoteElection |
P26341
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1936 Kansas gubernatorial election, isPopularVoteElection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularVoteElection Context triple: [1936 Kansas gubernatorial election, isPopularVoteElection, true]
-
A.
smithPopularVote
Indicates that Smith received a specified number or share of votes in a popular vote election or ballot.
-
B.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
C.
popularVoteOutcome
Indicates the result of a popular vote, specifying which option or candidate received the majority or winning share of votes.
-
D.
popularVoteType
chosen
Indicates the specific method or category by which a popular vote is conducted or classified in an election or decision process.
-
E.
popularVoteUsedFor
Indicates that the outcome of a popular vote is used as the basis or input for determining or deciding something.
- 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_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.