Triple
T35849858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | רצועת עזה |
E1036317
|
entity |
| Predicate | מאופיינת ב |
P96190
|
FINISHED |
| Object | עימותים מתמשכים בין ישראל לארגונים פלסטיניים חמושים |
—
|
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: עימותים מתמשכים בין ישראל לארגונים פלסטיניים חמושים | Statement: [רצועת עזה, מאופיינת ב, עימותים מתמשכים בין ישראל לארגונים פלסטיניים חמושים]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מאופיינת ב Context triple: [רצועת עזה, מאופיינת ב, עימותים מתמשכים בין ישראל לארגונים פלסטיניים חמושים]
-
A.
מאופיין ב
chosen
Indicates that something is characterized or defined by a particular feature, quality, or property.
-
B.
מאפיין מסורתי
Indicates a traditional characteristic or attribute that is typically associated with something based on long-standing customs or heritage.
-
C.
מפורטים_ב
Indicates that specific details or components of one entity are listed or elaborated within another entity.
-
D.
מושפע מ
Indicates that one entity is affected or influenced by another entity or factor.
-
E.
باب
Indicates a relationship where one entity serves as a door, gate, or entry point to another entity, allowing or controlling access between them.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.