Triple
T32954850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1966 United States Senate election in Michigan |
E843069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | election in Michigan |
C60767
|
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: election in Michigan Context triple: [1966 United States Senate election in Michigan, instanceOf, election in Michigan]
-
A.
election in Massachusetts
An election in Massachusetts is a formal process in which eligible voters in the state choose public officials or decide policy questions through ballots administered under Massachusetts election laws and regulations.
-
B.
election in Connecticut
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.
-
C.
election in New Jersey
An election in New Jersey is a formal process in which eligible voters in the state select candidates for public office or decide on public questions through ballots administered under New Jersey’s election laws and procedures.
-
D.
election in Maine
An election in Maine is a formal process in which eligible Maine voters select public officials or decide policy questions through ballots conducted under the state’s specific laws and procedures.
-
E.
election in Idaho
An election in Idaho is a formal process in which eligible Idaho voters select candidates for public office or decide on ballot measures at the local, state, or federal level according to state election laws and procedures.
- F. None of above. chosen
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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:21 a.m.