Triple
T5213689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fall Gelb (original variant) |
E117696
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German strategic plan |
C10085
|
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: German strategic plan Context triple: [Fall Gelb (original variant), instanceOf, German strategic plan]
-
A.
Nazi Germany expansion
Nazi Germany expansion refers to the aggressive territorial and political enlargement of Germany under Adolf Hitler from 1938 to 1941 through annexations, invasions, and occupations that precipitated and escalated World War II in Europe.
-
B.
Wehrmacht high command
chosen
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.
Kriegsmarine operation
A Kriegsmarine operation is a coordinated naval action planned and executed by Nazi Germany’s navy during World War II to achieve specific military, strategic, or logistical objectives at sea.
-
D.
German field army
A German field army is a large, operational-level military formation of the German armed forces, typically composed of multiple corps and supporting units, organized to conduct sustained land campaigns in a defined theater of war.
-
E.
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.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:47 p.m.