Persian Wars Marathon Salamis Plataea Chronology Lookup
Offline bounded reference card: Conventional Persian-War milestones include Marathon490 BCE, Salamis480 BCE, and Plataea479 BCE. References Herodotus, Histories6,8,9. These are nominal chronology anchors, not exact day conversions or a complete war timeline.
Description
Chronology anchors help organize the Persian Wars.
Chronology anchors help organize the Persian Wars.1
Nominal year labels do not supply exact converted days or a complete military timeline. Use Persian Wars Marathon Salamis Plataea Chronology Lookup to read a supported reference-card topic.
When to use Persian Wars Marathon Salamis Plataea Chronology Lookup
Use Persian Wars Marathon Salamis Plataea Chronology Lookup to read a supported reference-card topic. Choose an exact supported token from the table, preserving punctuation and capitalization.
How to use Persian Wars Marathon Salamis Plataea Chronology Lookup and understand its results
- Choose an exact supported token from the table, preserving punctuation and capitalization.
- Enter Topic using the field table and validation rules below, then run the tool.
- Read Text in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
- Read the limitations topic as well as the summary; use the reference topic to locate the underlying source. Correct unsupported tokens before rerunning.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| topic | Topic | string | Required; constraints below |
Enter one of the exact supported topic tokens listed below. The implementation performs a case-sensitive own-key lookup and returns the stored text unchanged. It does not fetch the cited books, search a corpus or inspect current policy. Unsupported tokens and added whitespace are input errors. Reference entries are bibliographic pointers rather than retrieved source passages; read the limitations alongside the summary. This bounded card is not a complete reference database.
returned text = storedTable[exactSupportedToken] Use the field order, units and branch conditions described above.
| Exact supported token | Stored reference text |
|---|---|
| summary | Conventional Persian-War milestones include Marathon490 BCE, Salamis480 BCE, and Plataea479 BCE. |
| reference | Herodotus, Histories6,8,9. |
| limitations | These are nominal chronology anchors, not exact day conversions or a complete war timeline. |
| Output field | Meaning | Value type |
|---|---|---|
| result | Object containing the named result fields below. | object |
| result.text | Stored text for the exact supported token; read summary, reference and limitations together. | string |
{
"input": {
"topic": "summary"
},
"output": {
"result": {
"text": "Conventional Persian-War milestones include Marathon490 BCE, Salamis480 BCE, and Plataea479 BCE."
}
}
}Limitations and assumptions
Nominal year labels do not supply exact converted days or a complete military timeline. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use Claudius Britannia ConquestAD 43 Rationale Lookup for a related task: An invasion's beginning and later imperial participation describe different stages.
Use Legion Cohort Centuria Maniple Hierarchy Numbers for a related task: Military hierarchy counts depend on the adopted cohort and centuria model.
References
Similar or alternative tools
- Claudius Britannia ConquestAD 43 Rationale Lookup
An invasion's beginning and later imperial participation describe different stages.
- Legion Cohort Centuria Maniple Hierarchy Numbers
Military hierarchy counts depend on the adopted cohort and centuria model.