Triple
T25830493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Tennessee gubernatorial election |
E650647
|
entity |
| Predicate | wasReelectionBid |
P52670
|
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: [2014 Tennessee gubernatorial election, wasReelectionBid, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasReelectionBid Context triple: [2014 Tennessee gubernatorial election, wasReelectionBid, true]
-
A.
incumbentRanForReelection
chosen
Indicates that a current officeholder sought to be elected again to the same position in a subsequent election.
-
B.
proposedExecutiveReelection
Indicates that an entity has formally put forward or supported the idea that a specific executive should be elected again to their position.
-
C.
reElectionOf
Indicates that an entity is being elected again to a position or office they have previously held.
-
D.
canBeReelected
Indicates that an individual currently holding an office or position is eligible to be chosen again for the same role in a subsequent election.
-
E.
wasCandidateIn
Indicates that an entity served as a candidate in a particular election, contest, or selection process.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6019917c88190aeef4467dd7749c2 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:38 a.m.