Triple
T37590680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secteur fortifié de Tarentaise |
E935252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maginot Line fortification |
C63984
|
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: Maginot Line fortification Context triple: [Secteur fortifié de Tarentaise, instanceOf, Maginot Line fortification]
-
A.
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.
-
B.
Alpine Maginot Line sector
chosen
The Alpine Maginot Line sector was a fortified stretch of France’s interwar defensive system built in the Alps to guard against potential Italian invasion through mountainous terrain.
-
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.
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.
-
E.
fortified bridge
A fortified bridge is a defensive structure that combines a crossing over a waterway or ravine with military features such as towers, battlements, and gates to control passage and resist 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.