Triple
T31044614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Przemyśl Fortress |
E791089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I fortification |
C15869
|
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: World War I fortification Context triple: [Przemyśl Fortress, instanceOf, World War I fortification]
-
A.
World War I site
chosen
A World War I site is a historically significant location directly associated with events, operations, or impacts of the First World War, such as battlefields, trenches, memorials, cemeteries, or military installations.
-
B.
military fortification system
A military fortification system is an integrated network of defensive structures, obstacles, and support facilities designed to protect territory, forces, and strategic assets from enemy attack.
-
C.
Nazi military installation
A Nazi military installation is a facility established and operated by the German armed forces under the Nazi regime for purposes such as training, command, logistics, weapons development, or the launching and support of military operations.
-
D.
World War I military formation
A World War I military formation is an organized grouping of soldiers, equipment, and command structures arranged for combat operations according to the tactical doctrines and technological constraints of the 1914–1918 conflict.
-
E.
World War I memorial
A World War I memorial is a monument or structure dedicated to commemorating the individuals and events associated with World War I, honoring the sacrifices and preserving the memory of those who served and suffered during the conflict.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.