Triple
T4823846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | June War |
E107773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Six-Day War |
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: Six-Day War Context triple: [June War, instanceOf, Six-Day War]
-
A.
Arab–Israeli conflict
chosen
The Arab–Israeli conflict is a long-standing political, territorial, and ideological struggle between Israel and various Arab states and Palestinian groups, centered on competing national claims to the land between the Jordan River and the Mediterranean Sea.
-
B.
Berlin Airlift
The Berlin Airlift was a massive Allied operation from 1948 to 1949 in which Western powers supplied West Berlin entirely by air after the Soviet Union blockaded all ground routes into the city.
-
C.
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.
-
D.
Mongol invasion of the Middle East
The Mongol invasion of the Middle East was a series of 13th- and 14th-century military campaigns by the Mongol Empire that devastated major Islamic centers, reshaped regional political structures, and facilitated new patterns of trade and cultural exchange across Eurasia.
-
E.
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.
- F. None of above.
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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.