Triple
T37567176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caucasus Line |
E933990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian imperial fortification system |
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: Russian imperial fortification system Context triple: [Caucasus Line, instanceOf, Russian imperial fortification system]
-
A.
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.
-
B.
Russian Empire military outpost
A Russian Empire military outpost is a fortified, often remote installation staffed by imperial troops to secure borders, project power, and maintain control over conquered or strategically important territories.
-
C.
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.
-
D.
European fort
A European fort is a fortified military structure, typically built from the medieval to early modern period, designed to defend strategic locations using walls, bastions, and other defensive works against enemy attacks.
-
E.
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.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.