Triple
T3868100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Declaration |
E91910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II declaration |
C873
|
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 declaration Context triple: [Moscow Declaration, instanceOf, World War II declaration]
-
A.
World War II front
A World War II front is a large-scale, geographically defined theater of military operations where opposing forces engaged in sustained combat and strategic maneuvers during the Second World War.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
World War II event
chosen
A World War II event is a historically significant occurrence between 1939 and 1945 that directly influenced the political, military, social, or economic course of the global conflict.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.