Triple
T27785999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehiya |
E700961
|
entity |
| Predicate | parliamentaryBodyContested |
P159504
|
FINISHED |
| Object | Knesset |
—
|
NE NERFINISHED |
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: Knesset | Statement: [Tehiya, parliamentaryBodyContested, Knesset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentaryBodyContested Context triple: [Tehiya, parliamentaryBodyContested, Knesset]
-
A.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
B.
areContestedIn
chosen
Indicates that something is the subject of dispute, challenge, or competition within a particular context, event, or process.
-
C.
parliamentaryConstituencyOfEvent
Indicates the parliamentary constituency within whose boundaries a given event takes place or is associated.
-
D.
portionOfSenateContested
Indicates the fraction of seats in a senate that are up for election or otherwise being contested during a given electoral cycle.
-
E.
electoralCompetitionWith
Indicates a relationship where two or more political actors or parties actively compete against each other in an electoral process for votes or office.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 5:24 p.m.