Triple
T26203971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Kansas gubernatorial election |
E655309
|
entity |
| Predicate | resultedInPartyControlChange |
P44678
|
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: [2018 Kansas gubernatorial election, resultedInPartyControlChange, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultedInPartyControlChange Context triple: [2018 Kansas gubernatorial election, resultedInPartyControlChange, yes]
-
A.
resultedInPartyChange
chosen
Indicates that one event or action caused a change in the political party affiliation of an entity.
-
B.
winningPartySeatChange
Indicates the change in the number of seats held by the winning party compared to a previous election or reference point.
-
C.
rulingPartyAfterElection
Indicates which political party holds governing power following the conclusion of an election.
-
D.
electionChange
Indicates a change in the outcome, status, or key parameters of an election between two points in time.
-
E.
defeatedIncumbentParty
Indicates that a political party won an election by defeating the party that previously held power or office.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 26, 2026, 8:49 p.m.