Triple
T18793571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Likud |
E459576
|
entity |
| Predicate | stanceOnPalestinianState |
P54133
|
FINISHED |
| Object | skeptical of fully sovereign Palestinian state |
—
|
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: skeptical of fully sovereign Palestinian state | Statement: [Likud, stanceOnPalestinianState, skeptical of fully sovereign Palestinian state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnPalestinianState Context triple: [Likud, stanceOnPalestinianState, skeptical of fully sovereign Palestinian state]
-
A.
positionOnArabIsraeliConflict
chosen
Indicates a stance or viewpoint that an entity holds regarding the Arab–Israeli conflict.
-
B.
effectOnPalestinians
Indicates the impact or consequences that an action, event, or condition has on Palestinians.
-
C.
designatedByPalestineAs
Indicates that an entity has been officially assigned a particular status, role, or label through a formal designation made by Palestine.
-
D.
returnToPalestine
Indicates that an entity goes back or is brought back to Palestine after having been elsewhere.
-
E.
statusOfJerusalem
Indicates the political or legal condition, control, or recognition of Jerusalem at a given time.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01cc0c0819098ef4326e82ff524 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.