Triple
T7808782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Voronezh (1942) |
E180624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Front battle of World War II |
C10195
|
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: Eastern Front battle of World War II Context triple: [Battle of Voronezh (1942), instanceOf, Eastern Front battle of World War II]
-
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.
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.
-
C.
batalla de la Segunda Guerra Mundial
chosen
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.
-
D.
World War II campaign
A World War II campaign is a coordinated series of military operations conducted over a specific period and geographic area, aimed at achieving strategic objectives within the broader context of the war.
-
E.
World War II offensive
A World War II offensive is a coordinated, large-scale military campaign conducted by one or more nations to seize strategic objectives, weaken enemy forces, or shift the balance of the war in a specific theater or front.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:36 p.m.