Triple
T12856721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Connecticut gubernatorial election |
E307474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Connecticut state election |
C27408
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Connecticut state election Context triple: [2018 Connecticut gubernatorial election, instanceOf, Connecticut state election]
-
A.
election in Connecticut
chosen
An election in Connecticut is a formal process in which eligible voters in the state choose public officials or decide public questions through ballots administered under Connecticut’s specific electoral laws and procedures.
-
B.
New York state election
A New York state election is a formal, scheduled process in which eligible voters in New York choose candidates for state offices and decide on statewide ballot measures according to state election laws and procedures.
-
C.
California state election
A California state election is a formal, statewide process in which eligible voters in California choose public officials, decide on ballot measures, and influence state governance according to established electoral laws and procedures.
-
D.
county of Connecticut
A county of Connecticut is an administrative geographic subdivision of the state used primarily for statistical and judicial purposes rather than local government.
-
E.
Missouri election
Missouri election refers to any formal voting process held within the state of Missouri to select public officials, decide ballot measures, or determine party nominees at the local, state, or federal level.
- F. None of above.
Provenance (1 batch)
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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:37 p.m.