Triple
T3478291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow defense zone |
E73428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defensive fortified area |
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: defensive fortified area Context triple: [Moscow defense zone, instanceOf, defensive fortified area]
-
A.
fortified building
A fortified building is a heavily constructed structure designed with defensive features such as thick walls, limited entry points, and protective battlements to resist attacks and provide security for its occupants.
-
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.
fortified tower
A fortified tower is a tall, strongly built defensive structure designed to provide elevated surveillance, protection, and control over the surrounding area.
-
D.
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.
-
E.
fortified quarter
A fortified quarter is a heavily defended district within a settlement, protected by walls, towers, and controlled access points to safeguard key populations, resources, or institutions.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:17 p.m.