Triple
T21013893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proposition 1A (2008) |
E517619
|
entity |
| Predicate | yesVoteShare |
P86317
|
FINISHED |
| Object | approximately 52.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 52.6% | Statement: [Proposition 1A (2008), yesVoteShare, approximately 52.6%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yesVoteShare Context triple: [Proposition 1A (2008), yesVoteShare, approximately 52.6%]
-
A.
yesVoteShareQuestion2
Indicates the proportion of total votes cast in favor of the "Yes" option on question 2 of a ballot or survey.
-
B.
yesVoteShareQuestion1
chosen
Indicates the proportion of total votes that were cast as "yes" in response to question 1.
-
C.
yesVotes
Indicates that a specified entity has cast or received affirmative votes in a decision-making or voting context.
-
D.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
E.
vote
Indicates that an entity formally expresses a choice or preference in a decision-making process, typically an election or poll.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc41d57881908b9ab17d1844a8d0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.