Triple
T18798833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Reindeer |
E459709
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German–Finnish military operation |
C28609
|
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–Finnish military operation Context triple: [Operation Reindeer, instanceOf, German–Finnish military operation]
-
A.
Soviet–Finnish War
The Soviet–Finnish War, also known as the Winter War (1939–1940), was a conflict in which the Soviet Union invaded Finland to secure territory and strategic depth, facing unexpectedly strong Finnish resistance in harsh winter conditions.
-
B.
Nazi military operation
chosen
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.
German military campaign
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.
-
D.
Heimosodat campaign
The Heimosodat campaign represents a series of early 20th-century Finnish volunteer military expeditions into neighboring regions inhabited by kindred Finnic peoples, aimed at supporting their independence or unification with Finland.
-
E.
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.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.