Triple
T16763012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Proposition 215 |
E407391
|
entity |
| Predicate | voteNoCount |
P5055
|
FINISHED |
| Object | approximately 4,301,960 |
—
|
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: approximately 4,301,960 | Statement: [California Proposition 215, voteNoCount, approximately 4,301,960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteNoCount Context triple: [California Proposition 215, voteNoCount, approximately 4,301,960]
-
A.
voteAgainst
chosen
Indicates that an entity formally expresses opposition to a proposal, decision, or candidate in a voting process.
-
B.
voteCount
Indicates the number of votes that have been cast for or associated with a particular item or option.
-
C.
nonVoting
Indicates that an entity participates in a group or organization without possessing the right to vote in its decisions.
-
D.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
E.
votesOnly
Indicates that an entity participates in a decision-making process solely by casting votes, without engaging in any other associated actions or roles.
- F. None of above.
Provenance (3 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abee862c819086d9bf01e623a8ce |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.