Triple
T16763009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Proposition 215 |
E407391
|
entity |
| Predicate | voteYesPercentage |
P75178
|
FINISHED |
| Object | approximately 55.6% |
—
|
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 55.6% | Statement: [California Proposition 215, voteYesPercentage, approximately 55.6%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteYesPercentage Context triple: [California Proposition 215, voteYesPercentage, approximately 55.6%]
-
A.
referendumYesPercentage
chosen
Indicates the percentage of votes cast in favor of the "yes" option in a referendum.
-
B.
votesForPercentage
Indicates the proportion of total votes that one entity receives in favor of another entity or option, usually expressed as a percentage.
-
C.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
D.
voterTurnoutPercentage
Indicates the proportion of eligible or registered voters who actually cast a ballot in a given election, expressed as a percentage.
-
E.
noVotesPercentage
Indicates the proportion of total votes that were cast as "no" in a given decision or election.
- 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.