Triple
T21013894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proposition 1A (2008) |
E517619
|
entity |
| Predicate | noVoteShare |
P66702
|
FINISHED |
| Object | approximately 47.4% |
—
|
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 47.4% | Statement: [Proposition 1A (2008), noVoteShare, approximately 47.4%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noVoteShare Context triple: [Proposition 1A (2008), noVoteShare, approximately 47.4%]
-
A.
nonVoting
Indicates that an entity participates in a group or organization without possessing the right to vote in its decisions.
-
B.
noVotesPercentage
chosen
Indicates the proportion of total votes that were cast as "no" in a given decision or election.
-
C.
recallNoVoteShare
Indicates that an entity’s share of votes in a recall context is measured or recorded excluding any votes classified as “no” votes.
-
D.
notElectedBy
Indicates that an individual or entity did not attain a position, role, or status through the voting or selection process of a specified group or electorate.
-
E.
voteAgainst
Indicates that an entity formally expresses opposition to a proposal, decision, or candidate in a voting process.
- 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.