Triple
T10188127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirpitz Plan |
E236963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German naval policy |
C17825
|
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 naval policy Context triple: [Tirpitz Plan, instanceOf, German naval policy]
-
A.
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.
-
B.
German military concept
chosen
A German military concept is a doctrinal idea or operational framework developed within German armed forces thought, guiding how military power is organized, deployed, and employed to achieve strategic and tactical objectives.
-
C.
Kriegsmarine admiral
A Kriegsmarine admiral is a high-ranking naval officer of Nazi Germany’s World War II navy, responsible for commanding major fleets, naval operations, and strategic maritime planning.
-
D.
naval theatre of war
A naval theatre of war is a maritime region, including its adjacent coastal areas and airspace, where naval forces conduct coordinated military operations during an armed conflict.
-
E.
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.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:12 p.m.