Triple
T15484413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minsk offensive (1944) |
E377006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet strategic operation |
C340
|
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: Soviet strategic operation Context triple: [Minsk offensive (1944), instanceOf, Soviet strategic operation]
-
A.
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.
-
B.
Nazi military operation
A Nazi military operation is a planned and coordinated action conducted by the armed forces of Nazi Germany to achieve specific strategic, tactical, or political objectives during its period of rule, particularly in World War II.
-
C.
Cold War operation
A Cold War operation is a covert or overt mission conducted by a state or its proxies during the Cold War era to advance strategic, ideological, or geopolitical objectives without escalating into full-scale direct conflict between superpowers.
-
D.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
E.
land offensive
A land offensive is a coordinated, large-scale military operation conducted primarily by ground forces to seize territory, defeat enemy formations, or achieve strategic objectives on land.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:45 a.m.