Triple
T25236624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Day War |
E632354
|
entity |
| Predicate | hasCeasefireBroker |
P26557
|
FINISHED |
| Object | Arab League |
—
|
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: Arab League | Statement: [Four Day War, hasCeasefireBroker, Arab League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCeasefireBroker Context triple: [Four Day War, hasCeasefireBroker, Arab League]
-
A.
ceasefireBrokeredBy
Indicates that a ceasefire agreement was arranged or facilitated through the mediation efforts of a specific party or entity.
-
B.
hasCeasefire
Indicates that a formal agreement has been established to temporarily stop hostilities or armed conflict between the involved parties.
-
C.
ceasefireBroker
chosen
Indicates that an entity mediates and facilitates an agreement to stop hostilities between conflicting parties.
-
D.
hasCeasefireHistoryWith
Indicates that two parties have previously been involved together in one or more ceasefire agreements or periods of formally suspended hostilities.
-
E.
hasCeasefireAttempt
Indicates that an effort or initiative has been made to establish, negotiate, or implement a ceasefire between parties in conflict.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 21, 2026, 1:07 p.m.