Triple
T37945045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | קו ירוק |
E946581
|
entity |
| Predicate | היה בתוקף כקו שביתת נשק עד |
P184072
|
FINISHED |
| Object | מלחמת ששת הימים ב-1967 |
—
|
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: מלחמת ששת הימים ב-1967 | Statement: [קו ירוק, היה בתוקף כקו שביתת נשק עד, מלחמת ששת הימים ב-1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: היה בתוקף כקו שביתת נשק עד Context triple: [קו ירוק, היה בתוקף כקו שביתת נשק עד, מלחמת ששת הימים ב-1967]
-
A.
hasCeasefire
Indicates that a formal agreement has been established to temporarily stop hostilities or armed conflict between the involved parties.
-
B.
ceasefireDuration
Indicates the length of time for which a ceasefire agreement between parties is intended to remain in effect.
-
C.
announcedPermanentCeasefire
Indicates that an entity has formally declared a ceasefire that is intended to be indefinite or lasting without a set end date.
-
D.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
E.
ceasefireEndTime
chosen
Indicates the specific time at which a ceasefire agreement is scheduled or observed to end.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.