Triple
T19354392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peel-Raamstelling defensive line (near Mill) |
E484102
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military fortification line |
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: military fortification line Context triple: [Peel-Raamstelling defensive line (near Mill), instanceOf, military fortification line]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
fortified settlement
A fortified settlement is a community enclosed by defensive structures such as walls, ramparts, or palisades, designed to protect its inhabitants and resources from 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:34 p.m.