Triple
T34096655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian frontier fort system in North Africa |
E874447
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | border 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: border fortification system Context triple: [Italian frontier fort system in North Africa, instanceOf, border 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.
border defense system
A border defense system is an integrated network of physical barriers, surveillance technologies, personnel, and response protocols designed to monitor, control, and protect a nation's boundaries from unauthorized crossings and external threats.
-
C.
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.
-
D.
border stronghold
A border stronghold is a heavily fortified military outpost positioned at the edge of a territory to defend against incursions, control crossings, and project power into adjacent lands.
-
E.
fortified enclosure
A fortified enclosure is a defended area surrounded by protective barriers such as walls, ramparts, or palisades, designed to control access and provide security against external threats.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:53 a.m.