Triple
T31044613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Przemyśl Fortress |
E791089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austro-Hungarian military fortification |
C876
|
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: Austro-Hungarian military fortification Context triple: [Przemyśl Fortress, instanceOf, Austro-Hungarian military fortification]
-
A.
military fortification system
chosen
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.
-
B.
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.
-
C.
line of fortifications
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.
-
D.
Vauban fortification
A Vauban fortification is a star-shaped, bastioned defensive work characterized by angular walls, layered outworks, and geometric design optimized to resist and control artillery fire.
-
E.
military architecture
Military architecture is the specialized design and construction of fortifications, defensive structures, and related military facilities intended to protect territories, control strategic points, and withstand or conduct armed attacks.
- 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.