Triple
T30367697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German summer offensive of 1943 |
E772464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht campaign |
C18722
|
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: Wehrmacht campaign Context triple: [German summer offensive of 1943, instanceOf, Wehrmacht campaign]
-
A.
German military campaign
chosen
A German military campaign is a coordinated series of strategic and tactical operations conducted by German armed forces to achieve specific political or military objectives during a defined period of conflict.
-
B.
Wehrmacht high command
The Wehrmacht high command was the central military leadership of Nazi Germany responsible for planning, directing, and coordinating the operations of the German armed forces during the Second World War.
-
C.
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.
-
D.
Eastern Front campaign
The Eastern Front campaign is a large-scale military operation or series of operations conducted on the eastern theater of war, typically involving prolonged, high-intensity ground combat across vast territories between major opposing powers.
-
E.
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.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:59 p.m.