Triple
T34910963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Connecticut gubernatorial election |
E1006863
|
entity |
| Predicate | electionForTerm |
P77824
|
FINISHED |
| Object | 2015–2019 |
—
|
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: 2015–2019 | Statement: [2014 Connecticut gubernatorial election, electionForTerm, 2015–2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionForTerm Context triple: [2014 Connecticut gubernatorial election, electionForTerm, 2015–2019]
-
A.
electedForTerm
chosen
Indicates that an entity has been chosen through an election to hold a position or office for a specified term or duration.
-
B.
electionForOffice
Indicates that an election event is held to select or fill a specific office or position.
-
C.
electionIs
Indicates that a particular event, process, or state qualifies as or constitutes an election.
-
D.
isThirdTermElectionFor
Indicates that an election is being held for a candidate’s third consecutive term in a given office or position.
-
E.
electionCycle
Indicates the recurring period or sequence of time in which elections are organized, conducted, and repeated for a given office or political system.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 3, 2026, 4 p.m.