Triple
T7706134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1922 California gubernatorial election |
E174620
|
entity |
| Predicate | hasBallotType |
P78405
|
FINISHED |
| Object | secret ballot |
—
|
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: secret ballot | Statement: [1922 California gubernatorial election, hasBallotType, secret ballot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBallotType Context triple: [1922 California gubernatorial election, hasBallotType, secret ballot]
-
A.
hasElectionType
Indicates the specific category or kind of election associated with a given electoral event or process.
-
B.
hasBallotLine
Indicates that an entity (typically a candidate or party) appears as a selectable option on a specific ballot line in an election.
-
C.
hasElectoralRollType
Indicates the specific category or type of electoral roll associated with an entity, such as general, special, or supplementary voter lists.
-
D.
appliesToElectionType
Indicates that a rule, condition, or attribute is relevant or applicable to a specific type or category of election.
-
E.
ballotStatus
Indicates the current state or outcome of a ballot within a voting or decision-making process.
- F. None of above. chosen
Provenance (4 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:03 p.m.