Triple
T9992045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himmelbett zone |
E196908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Kammhuber Line |
C875
|
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: component of the Kammhuber Line Context triple: [Himmelbett zone, instanceOf, component of the Kammhuber Line]
-
A.
line of fortifications
chosen
A line of fortifications is a connected series of defensive structures, such as walls, trenches, and strongpoints, designed to protect a territory or position by forming a continuous or coordinated barrier against attack.
-
B.
Wehrmacht position
A Wehrmacht position is a designated location or role within the German armed forces of Nazi Germany during World War II, encompassing specific duties, rank, and tactical responsibilities in military operations.
-
C.
Luftwaffe command position
A Luftwaffe command position is an organizational role within the German air force hierarchy responsible for directing air operations, managing resources, and implementing strategic and tactical decisions.
-
D.
section of the Berlin Wall
A section of the Berlin Wall is a preserved or reconstructed fragment of the former fortified barrier that once divided East and West Berlin, serving as a historical artifact and symbol of Cold War division and reunification.
-
E.
Luftwaffe wing
A Luftwaffe wing is a major operational air unit of the German Air Force, typically composed of several squadrons or groups equipped and organized to perform specific missions such as air defense, strike, or reconnaissance.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:50 p.m.