Triple
T37472395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominance Keep |
E931185
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fortified subzone |
C17842
|
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: fortified subzone Context triple: [Dominance Keep, instanceOf, fortified subzone]
-
A.
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.
-
B.
fortified battlefield sector
A fortified battlefield sector is a defined area of the front line that has been heavily strengthened with defensive structures, obstacles, and support assets to resist enemy attack and control key terrain.
-
C.
fortified core
A fortified core is a heavily protected central area or subsystem designed to maintain critical functions and security even under extreme external threats or failures.
-
D.
fortified enclosure
chosen
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 pass
A fortified pass is a strategically important narrow route through difficult terrain that has been strengthened with defensive structures to control movement and resist enemy forces.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.