battle
Let an agent describe battles as historical events with sourced facts, place them in campaigns and wars, present contested accounts and casualty figures with attribution, and keep to history rather than operational military guidance.
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Record The facts of a battle.
Facts
Date, place, forces.
Facts
Facts.
- When and where was the battle, who fought, who commanded, and what forces were engaged, from which sources? provenance
- Is the question about a battle, a siege, a campaign or a war? boundary
Outcome
Outcome and losses.
Outcome
Outcome.
- What was the outcome, and what casualty estimates exist, with ranges and sources? measurement
- Are contested figures presented with attribution? boundary
Context Campaign and consequences.
Campaign
Campaign context.
Campaign
Campaign.
- How does the battle fit into its campaign and war? provenance
- Which entry fits the war? action
Consequences
Consequences.
Consequences
Consequences.
- What were the political and military consequences, as assessed by historians? provenance
- Is the assessment attributed? boundary
Interpret Historiography and memory.
Historiography
Interpretations.
Historiography
Historiography.
- How have historians interpreted the battle, and where do they disagree? provenance
- Which references are standard? provenance
Memory
Commemoration.
Memory
Memory.
- How is the battle commemorated, and how do national narratives differ, with attribution? provenance
- Is the presentation neutral? boundary
Site Battlefield and law.
Battlefield
The site.
Battlefield
Battlefield.
- Where is the battlefield, and how is it protected or studied by archaeology? provenance
- Which entry fits battlefield archaeology? action
Law
Law of war.
Law
Law.
- Which rules of international humanitarian law bear on the conduct of battles, in general terms? provenance
- Is the user asking for operational military guidance, which the model does not give? boundary
Classifiers Filled
- Family
- Thing Registry
- Category
- Activities and processes
- Entry kind
- thing
- Plane
- ACT
- Domain
- ACT.ACT
- Other names and narrower kinds
- ochimusha-gari, grypomachy, first battle, decisive warfare, naval battle, tank battle, battle of the Paraguayan War, medieval battle, main battle, legendary battle, Baroud, encounter battle
What it is Filled
A combat between armed forces at a particular place and time within a war or campaign, from a skirmish to a multi-day engagement on land, at sea or in the air, recorded by historians with its date, location, belligerents, commanders, forces, outcome and consequences.
Why it exists Filled
Let an agent describe battles as historical events with sourced facts, place them in campaigns and wars, present contested accounts and casualty figures with attribution, and keep to history rather than operational military guidance.
Distinguishing features Filled
- Bounded engagement within a wider conflict
- Recorded with belligerents, commanders and outcome
- Outcome and casualties often contested
- Named after places
What robots and AI may and may not do Filled
Must not
- State casualty figures without sources or present one estimate as certain.
- Glorify killing or present a battle as entertainment detached from its victims.
- Present one nation's narrative as the only truth.
- Turn historical description into tactical guidance for present-day violence.
Only with a human decision
- Publishing an account of a recent battle where people are still grieving or contesting it.
May
- Describe a battle's date, place, forces and outcome from historical sources.
- Present differing national accounts of a battle side by side.
Moral aspects Filled
- Battles cost lives; accounts of them shape identity and grievance for generations.
- Distorted histories are used to justify new conflicts.
Who is affected
- Descendants of combatants and civilians
- Communities in contested regions
- Students of history
Owners Filled
Steward
Nobody owns a battle; historians, archives and commemoration bodies keep its record.
Master systems
- Military and national archives
- War grave registers
Links to other meta-models Filled
parent
- Q123349687 - registry parent class
- Q13418847 - registry parent class
- Q350604 - registry parent class
- Q645883 - registry parent class
- Q650711 - registry parent class
related
- armed conflict - a bounded engagement
- war - the wider conflict
- siege - a prolonged operation against a fortified place
- military history - the discipline
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.battle
- Wikidata: Q178561 (https://www.wikidata.org/wiki/Q178561)
- conventional name: Battle of place, date as used by historians
Direct properties not applicable Not applicable
Not applicable
Plane ACT: no invented physical properties.
Recognition optional Filled
- Armed engagement bounded in place and time
- Part of a war or campaign
- A siege, a massacre and a war are related but distinct entries
- Not a physical object; commemorated by sites, monuments and records.
Capabilities and actions required Filled
- record date, place, belligerents and outcome from sources
- place a battle within its war and campaign
- present contested figures and interpretations with attribution
- route to the specific battle entry
Hazards and failure modes required Filled
- Casualty figures stated without sources
- National narratives presented as fact
- Glorification or operational detail instead of history
- Confusing battles with wars or campaigns
Standards and interfaces required Filled
- International humanitarian law governs the conduct of hostilities
- War graves and battlefield heritage protection
- Archival and historiographical standards
Context of use required Filled
- Not applicable; an event in war.
- land battles
- naval battles
- air battles
- sieges and assaults, related
- decisive and indecisive battles as historiographical categories
- battles by era and war
Sources Filled
- Wikidata item Q178561: battle - identity and sense of the item
- Wikipedia: Battle - general description of the item
Open questions
- Should each battle be a separate entry only?
- How should casualty estimates be recorded with ranges and sources?
- The registry entry has merged aliases naming specific engagements and Japanese terms; should they be split off?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q178561/spec.json