Triple
T6532422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suez Canal front |
E152262
|
entity |
| Predicate | underCeasefire |
P40461
|
FINISHED |
| Object | UN-brokered ceasefire of August 1970 |
—
|
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: UN-brokered ceasefire of August 1970 | Statement: [Suez Canal front, underCeasefire, UN-brokered ceasefire of August 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underCeasefire Context triple: [Suez Canal front, underCeasefire, UN-brokered ceasefire of August 1970]
-
A.
endedCeasefire
Indicates that a previously established ceasefire between parties has been terminated or broken.
-
B.
calledCeasefire
Indicates that an agreement has been made to temporarily stop hostilities or fighting between the involved parties.
-
C.
resumedCeasefire
Indicates that a previously halted ceasefire between parties has been restarted or put back into effect.
-
D.
hasCeasefire
chosen
Indicates that a formal agreement has been established to temporarily stop hostilities or armed conflict between the involved parties.
-
E.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbe168881908ffefc4962e2893d |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.