Triple
T13761739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 Pennsylvania gubernatorial election |
E330625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pennsylvania state election |
C34140
|
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: Pennsylvania state election Context triple: [2006 Pennsylvania gubernatorial election, instanceOf, Pennsylvania state election]
-
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.
gubernatorial election
A gubernatorial election is a political contest in which voters choose the governor, the chief executive of a state or similar subnational jurisdiction.
-
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.
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.
-
E.
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.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:09 p.m.