Triple
T23987566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel and Egypt |
E604979
|
entity |
| Predicate | subsequentWar |
P154517
|
FINISHED |
| Object | Suez Crisis of 1956 |
—
|
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: Suez Crisis of 1956 | Statement: [Israel and Egypt, subsequentWar, Suez Crisis of 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentWar Context triple: [Israel and Egypt, subsequentWar, Suez Crisis of 1956]
-
A.
warName
Indicates the specific name or title assigned to a particular war or armed conflict.
-
B.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
-
C.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
D.
majorWar
Indicates a large-scale, intense armed conflict between major powers or involving substantial military forces and widespread impact.
-
E.
secondMajorWar
Indicates that the referenced conflict is the second major war in a series or sequence of large-scale wars involving the same primary parties or context.
- F. None of above. chosen
Provenance (4 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38838f481909a52fccd392a92df |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:36 p.m.