Triple
T24575158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Führer der Zerstörer |
E608083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kriegsmarine command |
C34496
|
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: Kriegsmarine command Context triple: [Führer der Zerstörer, instanceOf, Kriegsmarine command]
-
A.
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.
-
B.
branch of the Kriegsmarine High Command
chosen
A branch of the Kriegsmarine High Command is an organizational subdivision responsible for directing specific naval functions—such as operations, logistics, intelligence, or training—within the overall command structure of Nazi Germany’s navy.
-
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.
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.
-
E.
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.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:29 a.m.