Triple
T17580067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli legislative election, 1969 |
E428176
|
entity |
| Predicate | party2VoteShare |
P73163
|
FINISHED |
| Object | 21.7% |
—
|
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: 21.7% | Statement: [Israeli legislative election, 1969, party2VoteShare, 21.7%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: party2VoteShare Context triple: [Israeli legislative election, 1969, party2VoteShare, 21.7%]
-
A.
secondPartyPopularVoteShare
chosen
Indicates the proportion of total popular votes received by the second party in an election.
-
B.
voteShareMainOpponent
Indicates the proportion of total votes received by the primary opposing candidate or party in an election.
-
C.
AlliancePopularVoteShare
Indicates the proportion of total votes received by a political alliance in an election relative to all valid votes cast.
-
D.
rulingPartyPopularVotePercentage
Indicates the percentage of the total popular vote received by the party currently in power or holding the ruling position.
-
E.
popularVoteShare
Indicates the proportion of all votes cast in an election that were received by a particular candidate, party, or option.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463cdb1608190a7e249ad6531b1dc |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.