Triple
T33111375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German High Seas Fleet |
E847340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | formation of the Imperial German Navy |
C64994
|
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: formation of the Imperial German Navy Context triple: [German High Seas Fleet, instanceOf, formation of the Imperial German Navy]
-
A.
formation of the Imperial German Army
The formation of the Imperial German Army refers to the unification and reorganization of the various German states' military forces into a centralized, Prussian-led national army following the creation of the German Empire in 1871.
-
B.
formation of the Volksmarine
The formation of the Volksmarine refers to the establishment and development of East Germany’s naval forces as the maritime branch of the National People’s Army, shaped by Cold War politics and Warsaw Pact military doctrine.
-
C.
Imperial German Navy facility
An Imperial German Navy facility is a shore-based installation, such as a dockyard, base, depot, or training center, operated by the Imperial German Navy to support, maintain, supply, and command its maritime forces.
-
D.
component of the Kriegsmarine
A component of the Kriegsmarine is any organizational, structural, or functional unit—such as a ship, fleet formation, base, or support service—that formed part of Nazi Germany’s navy between 1935 and 1945.
-
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. chosen
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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:27 a.m.