Triple
T1289679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab–Israeli War of 1948 |
E27516
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arab–Israeli conflict |
C6935
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Arab–Israeli conflict Context triple: [Arab–Israeli War of 1948, instanceOf, Arab–Israeli conflict]
-
A.
post–Yom Kippur War diplomacy
Post–Yom Kippur War diplomacy refers to the series of negotiations, shuttle missions, and agreements among Israel, Egypt, Syria, the United States, and other actors after the 1973 war that reshaped Middle Eastern borders, security arrangements, and great-power influence in the region.
-
B.
Palestinian territory
Palestinian territory refers to the geographic areas of the West Bank, including East Jerusalem, and the Gaza Strip that are claimed by Palestinians for a future independent state and are subject to ongoing political and territorial disputes.
-
C.
Zionist movement
The Zionist movement is a political and ideological movement that emerged in the late 19th century advocating for the establishment and support of a Jewish homeland in the historic Land of Israel.
-
D.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
E.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
- F. None of above. chosen
Provenance (1 batch)
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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.