Triple
T8070273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Defense Area |
E188352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military defensive zone |
C16458
|
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 defensive zone Context triple: [Berlin Defense Area, instanceOf, military defensive zone]
-
A.
military-controlled zone
chosen
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
-
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.
protective zone
A protective zone is a designated area or boundary established to shield people, assets, or environments from potential harm, hazards, or unauthorized influence.
-
D.
demilitarized zone arrangement
A demilitarized zone arrangement is a structured agreement or configuration that establishes a buffer area where military forces, weapons, or hostile activities are restricted or prohibited to reduce conflict and enhance security between opposing parties.
-
E.
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.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:27 p.m.