Triple
T4186978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armistice of 22 June 1940 |
E88335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II armistice |
C3616
|
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: World War II armistice Context triple: [Armistice of 22 June 1940, instanceOf, World War II armistice]
-
A.
World War I armistice
The World War I armistice is the formal agreement signed on November 11, 1918, between the Allies and Germany that ended the fighting on the Western Front and effectively brought World War I to a close pending a final peace treaty.
-
B.
World War II conference
A World War II conference is a high-level diplomatic meeting held among Allied or Axis leaders during the war to coordinate military strategy, negotiate political arrangements, and shape postwar plans.
-
C.
military surrender
Military surrender is the formal act by which an armed force or nation yields control and ceases resistance to an opposing force, typically under agreed conditions.
-
D.
batalla de la Segunda Guerra Mundial
Una batalla de la Segunda Guerra Mundial es un enfrentamiento militar específico, terrestre, naval o aéreo, ocurrido entre 1939 y 1945, que involucró fuerzas de las potencias aliadas y/o del Eje con objetivos estratégicos definidos dentro del conflicto global.
-
E.
wartime settlement
chosen
A wartime settlement is an agreement or arrangement reached during or immediately after armed conflict that defines the terms for ending hostilities, addressing territorial or political disputes, and establishing conditions for postwar order.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:45 p.m.