Home › Entities › battle › Battle of Zaozernaya Hill

Battle of Zaozernaya Hill

Event battle Q21636228
Press Enter · cited answer in seconds

Battle of Zaozernaya Hill

Summary

Battle of Zaozernaya Hill is a battle[1].

Key Facts

  • Battle of Zaozernaya Hill's instance of is recorded as battle[2].
  • Battle of Zaozernaya Hill's location is recorded as Zaozyornaya[3].
  • Battle of Zaozernaya Hill's part of is recorded as Soviet–Japanese border conflicts[4].
  • Battle of Zaozernaya Hill's point in time is recorded as +1938-08-06T00:00:00Z[5].
  • Battle of Zaozernaya Hill's Google Knowledge Graph ID is recorded as /g/11bw4rmy0b[6].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [2] ↑ . wikidata.org.
  2. [3] ↑ . wikidata.org.
  3. [4] ↑ . wikidata.org.
  4. [5] ↑ . wikidata.org.
  5. [6] ↑ . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). Battle of Zaozernaya Hill. Retrieved May 3, 2026, from https://4ort.xyz/entity/battle-of-zaozernaya-hill
MLA “Battle of Zaozernaya Hill.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/battle-of-zaozernaya-hill.
BibTeX @misc{4ortxyz_battle-of-zaozernaya-hill_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{Battle of Zaozernaya Hill}}, year = {2026}, url = {https://4ort.xyz/entity/battle-of-zaozernaya-hill}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): Battle of Zaozernaya Hill — https://4ort.xyz/entity/battle-of-zaozernaya-hill (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/battle-of-zaozernaya-hill · Last refreshed: