Triple
T37674134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | אמת |
E938043
|
entity |
| Predicate | voterUsage |
P110753
|
FINISHED |
| Object | marked by voters to choose HaAvoda |
—
|
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: marked by voters to choose HaAvoda | Statement: [אמת, voterUsage, marked by voters to choose HaAvoda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voterUsage Context triple: [אמת, voterUsage, marked by voters to choose HaAvoda]
-
A.
numberOfVoters
Indicates the total count of individuals who participated in a particular vote or election.
-
B.
usesVoterRegistration
Indicates that one entity relies on or applies another entity’s voter registration information for a particular purpose or process.
-
C.
hasVoterParticipation
Indicates that there is a relationship where an entity participates as a voter in an election or voting process.
-
D.
usesVotingBallots
chosen
Indicates that one entity conducts or participates in a voting process by employing ballots as the method for casting votes.
-
E.
popularVoteUsedFor
Indicates that the outcome of a popular vote is used as the basis or input for determining or deciding something.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e8d3388190876fda332d23e901 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.