Greek Aorist vs Imperfect Aspect Classifier
Describe conventional aspect contrast of independently annotated Ancient Greek aorist/imperfect, no actual verb-form parsing or contextual temporal guarantee.
Description
Verbal aspect concerns how an event is viewed rather than its objective length.
Verbal aspect concerns how an event is viewed rather than its objective length.1
Aorist and imperfect labels do not imply that every event was brief or repeated. Use Greek Aorist vs Imperfect Aspect Classifier to read a supported reference-card topic.
When to use Greek Aorist vs Imperfect Aspect Classifier
Use Greek Aorist vs Imperfect Aspect Classifier to read a supported reference-card topic. Choose an exact supported token from the table, preserving punctuation and capitalization.
How to use Greek Aorist vs Imperfect Aspect Classifier and understand its results
- Choose an exact supported token from the table, preserving punctuation and capitalization.
- Enter Independently annotated tense using the field table and validation rules below, then run the tool.
- Read Default Aspect Description in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
- Read the selected stored entry in the context described below. The tool does not retrieve additional source material; correct unsupported tokens before rerunning.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| independentlyAnnotatedTense | Independently annotated tense | string | Required; constraints below |
Enter one of the exact supported independentlyAnnotatedTense 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. The entries are stored summaries rather than retrieved source passages; read the stated scope and assumptions alongside the selected topic. 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 |
|---|---|
| aorist | perfective view of the event, not necessarily short duration |
| imperfect | imperfective past view, not necessarily repeated action |
| Output field | Meaning | Value type |
|---|---|---|
| result | Object containing the named result fields below. | object |
| result.defaultAspectDescription | Default Aspect Description | string |
{
"input": {
"independentlyAnnotatedTense": "aorist"
},
"output": {
"result": {
"defaultAspectDescription": "perfective view of the event, not necessarily short duration"
}
}
} Limitations and assumptions
Aorist and imperfect labels do not imply that every event was brief or repeated. 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 Subjunctive Purpose vs Result Clause Checker for a related task: Purpose and result clauses describe different semantic relationships.
Use Greek Article Paradigm Agreement Checker for a related task: Article-noun agreement compares grammatical case, number and gender.
References
Similar or alternative tools
- Subjunctive Purpose vs Result Clause Checker
Purpose and result clauses describe different semantic relationships.
- Greek Article Paradigm Agreement Checker
Article-noun agreement compares grammatical case, number and gender.