Triple
T33608727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 United States gubernatorial elections |
E860927
|
entity |
| Predicate | republicanNetChange |
P116268
|
FINISHED |
| Object | +8 |
—
|
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: +8 | Statement: [1986 United States gubernatorial elections, republicanNetChange, +8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: republicanNetChange Context triple: [1986 United States gubernatorial elections, republicanNetChange, +8]
-
A.
republicanParty
Indicates that an entity is affiliated with, belongs to, or is a member/supporter of the Republican Party.
-
B.
netSeatChangeForRepublicanParty
chosen
Indicates the overall gain or loss in the number of seats held by the Republican Party after an election or series of elections.
-
C.
includedRepublic
Indicates that one entity is a republic that is contained within, or forms part of, another political or administrative entity.
-
D.
republicanPopularVoteShare
Indicates the proportion of total votes in an election that were cast for the Republican Party.
-
E.
politicalShift
Indicates a change in an entity’s political position, alignment, or governing structure over time.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f7e0161c819082821d70da67d5d3 |
completed | May 3, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.