Triple
T13730403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohenfriedberger Marsch |
E329781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German military march |
C12182
|
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 military march Context triple: [Hohenfriedberger Marsch, instanceOf, German military march]
-
A.
military march
chosen
A military march is a disciplined, rhythmic procession of armed forces, often accompanied by structured music, used for ceremonial display, training, or coordinated movement.
-
B.
Wehrmacht signals unit
A Wehrmacht signals unit was a specialized German military formation responsible for establishing, operating, and maintaining communications networks—such as radio, telephone, and telegraph—between command elements and combat units during World War II.
-
C.
German army detachment
A German army detachment is a temporary, task-organized military formation separated from a larger parent unit to conduct specific operations under its own command structure.
-
D.
Prussian Army regiment
A Prussian Army regiment is a military unit of the Kingdom of Prussia, typically composed of several battalions or squadrons, organized under a unified command structure for tactical, administrative, and ceremonial purposes.
-
E.
German Army regiment
A German Army regiment is a mid-sized military unit typically composed of several battalions, providing a structured formation for combat, support, and administrative functions within the German land forces.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:55 p.m.