Triple
T37495091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secteur fortifié des Alpes-Maritimes |
E931803
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French 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: French military fortification Context triple: [Secteur fortifié des Alpes-Maritimes, instanceOf, French military fortification]
-
A.
French military residential complex
A French military residential complex is a secured, purpose-built housing area that provides accommodation and essential communal facilities for members of the French armed forces and their families.
-
B.
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.
-
C.
French military engineering service
The French military engineering service is the branch of the armed forces responsible for designing, constructing, maintaining, and protecting military infrastructure, fortifications, and field works to support national defense and operational capabilities.
-
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.
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.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.