Triple
T37674133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | אמת |
E938043
|
entity |
| Predicate | ballotFunction |
P30499
|
FINISHED |
| Object | identifies party on ballot |
—
|
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: identifies party on ballot | Statement: [אמת, ballotFunction, identifies party on ballot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballotFunction Context triple: [אמת, ballotFunction, identifies party on ballot]
-
A.
ballotOf
Indicates that one entity is the ballot associated with, used by, or belonging to another entity (such as a voter, election, or voting event).
-
B.
voterFunction
Indicates a relationship where an entity serves in the role or capacity of a voter within a decision-making or electoral process.
-
C.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
D.
ballotStructure
chosen
Indicates how options, candidates, or choices are organized and presented on a ballot for selection.
-
E.
electionFunction
Indicates a relationship where an entity serves as the mechanism, process, or method by which an election is conducted or its outcome is determined.
- 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.