Triple
T4182743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet summer offensive of 1944 |
E88231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | campaign of the Eastern Front of World War II |
C635
|
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: campaign of the Eastern Front of World War II Context triple: [Soviet summer offensive of 1944, instanceOf, campaign of the Eastern Front of World War II]
-
A.
World War II campaign
chosen
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.
-
B.
Soviet campaign
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
-
C.
campaign of the Russian Civil War
A campaign of the Russian Civil War is a coordinated series of military operations conducted by opposing factions over a specific region and period, aimed at achieving strategic political and territorial objectives within the broader conflict.
-
D.
phase of World War II
A phase of World War II is a distinct, time-bounded period of the conflict characterized by specific strategic objectives, major campaigns, and shifts in military, political, or economic conditions.
-
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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:45 p.m.