Triple
T10107522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1944 United States Senate election in Connecticut |
E216358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | election in Connecticut |
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: election in Connecticut Context triple: [1944 United States Senate election in Connecticut, instanceOf, election in Connecticut]
-
A.
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.
-
B.
electoral college
The electoral college is an indirect voting system in which designated electors, chosen by voters in each state or region, formally select the head of state or government rather than the officeholder being elected by a direct popular vote.
-
C.
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.
-
D.
2019 election
The 2019 election class represents a specific electoral event held in the year 2019, encapsulating its candidates, parties, results, and associated political context.
-
E.
presidential election
A presidential election is a formal, periodic process in which eligible voters select a head of state or government, typically through a structured system of campaigns, ballots, and vote counting governed by constitutional or legal rules.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.