Triple
T14786660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marinewaffenamt |
E347543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kriegsmarine organization |
C32086
|
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 organization Context triple: [Marinewaffenamt, instanceOf, Kriegsmarine organization]
-
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.
Wehrmacht organization
chosen
The Wehrmacht organization is a structured representation of the hierarchical, functional, and administrative components of Nazi Germany’s unified armed forces, including their command chains, unit types, and operational relationships.
-
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.
U-boat
A U-boat is a German military submarine, especially those used in the World Wars for stealthy naval warfare, commerce raiding, and blockades.
-
E.
Scharnhorst-class battleship
The Scharnhorst-class battleship was a pair of fast, heavily armed German capital ships built in the late 1930s that combined relatively light main guns with strong armor and high speed for commerce raiding and fleet actions in World War II.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.