Battle of Palnadu
12th-century battle in Southern India
The Battle of Palnadu took place sometime in the years 1178–1182 CE, between a Haihaya king called Nalagamaraju, who ruled the then Gurazala kingdom, and his step-brother Malidevaraju who ruled the then Macherla kingdom. Nalagamaraju was supported by Nayakuralu Nagamma while Malidevaraju was supported by Palanati Brahmanaidu| alias Seelam Brahmanaidu from Velama Caste. The story, as presented in both oral and written narratives, is largely corroborated by inscriptional records.
Background
Palnadu is a region located in Palnadu district and covering some part of Prakasam district. It is spread over the present-day areas of Macherla, Karampudi, Gurazala and Narasaraopeta in the Palnadu district and Markapur in the Prakasam district of the state of Andhra Pradesh, India.
When Anuguraju of the Haihayas migrated to the Andhra area from Jabalpur in Madhya Pradesh, he clashed with the Velanati Chodas of Velanadu who ruled from Chandavolu. Velanati Gonkaraju installed Anuguraju as king of Palnadu at Gurajala after giving his daughter Mailama Devi to him in marriage. As Anuguraju was non-Telugu-speaking and had migrated to Andhra area only at that time, and unfamiliar with the local people, Gonkaraju appointed Seelam Dodda Naidu of Recherla Gotra as his minister to guide him. Anugu Raju had 2 more wives, Viravidya Devi and Bhoorama Devi. Anuguraju was however childless and adopted the eldest son of his minister Dodda Naidu.
Begin with the source’s own compact description: “Battle of Palnadu” is 12th-century battle in Southern India. The dossier treats that line as a proposition to test through Battle, Palnadu and 12th-century, not as a finished interpretation.
Why this record matters
The phrase “12th-century battle in Southern India” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Sep 19, 2026. The linked authority identifier is Q16315683. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1178 and 1182.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Battle of Palnadu”, its source revision and the description used here.
- Expand the search: follow Battle of Palnadu primary sources, Battle of Palnadu archive and Battle research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Battle of Palnadu”?
- What chronology connects this entry to wider political or social change?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Battle of Palnadu” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.