How To Read Hebrew Morphology In Maqor

Hebrew morphology describes the grammatical form of a word. In Maqor, a compact code is shown in the verse block, while the word popup can expand that code into a fuller description.

Why compact codes exist

What morphology can tell you

Morphology can indicate whether a form is a noun, verb, particle, article, conjunction, preposition, or other grammatical category. For verbs, it can indicate stem, conjugation, person, gender, and number. For nouns and adjectives, it can indicate gender, number, state, or other relevant grammatical information depending on the source data.

What morphology cannot do alone

A morphology code does not determine theology, discourse function, or translation by itself. It is one piece of evidence. The same grammatical form can function differently in different contexts. Maqor therefore shows morphology alongside lemma, lexical information, source text, and translation support.

Example use

In Genesis 1:1, a reader can compare the Hebrew surface form, the lemma, and the morphology code to see how the word contributes to the clause. The compact code gives a quick grammatical signal; the popup gives the longer explanation.

Reading morphology as evidence

A morphology code should be treated as evidence about form, not as a complete interpretation. If a Hebrew verb is tagged with stem, conjugation, person, gender, and number, that helps the reader identify what kind of form is present. It does not by itself decide how the clause should be preached, translated, or connected to a doctrinal argument. The form narrows the discussion; it does not end the discussion.

Why prefixes matter

Hebrew often attaches short grammatical elements to a word. A conjunction, article, or preposition can be written as part of the same surface token. If an interlinear display removes those elements too aggressively, the user may no longer see the word as it appears in the text. Maqor keeps the surface form intact and uses the popup to explain attached elements where possible.

Common beginner mistakes

One common mistake is to read a lemma as if it were the exact word in the verse. The lemma is a reference form, not necessarily the surface form. Another mistake is to assume that a gloss gives the only possible translation. A third mistake is to ignore number, gender, or state because those features do not always map cleanly into English. Morphology helps prevent those mistakes when it is read alongside the source word.

Why Maqor keeps raw morphology available

Normalization makes the interface easier to use, but the raw source code remains important for verification. If a user notices a mismatch, the raw code can show whether the problem came from the upstream data, from Maqor's normalization, or from the display layer. This makes corrections more precise and helps keep the project accountable.

How to read an expanded breakdown

When the popup expands a compact code, read it from broad category to specific features. A verb breakdown might begin with "Verb," then identify the stem, conjugation, person, gender, and number. A noun breakdown might identify noun type, gender, number, and state. The final compact code remains useful because it lets the reader compare the expanded explanation with the abbreviated form shown in the verse.

This approach also keeps the app consistent across languages. Greek, Hebrew, and Syriac morphology do not have identical categories, but the user should still be able to recognize the same pattern: compact code in the verse, expanded explanation in the popup, raw source value available for verification, and source-specific limitations documented in the methodology.

Why morphology must be checked against context

A morphology label can identify a form, but context determines how that form contributes to meaning. For example, a verb form may be grammatically clear while its discourse function remains debated. A noun may be grammatically definite or construct, but the interpretive significance depends on the phrase and passage. Maqor therefore presents morphology as a starting point for reading, not as a final conclusion.

For a full example, see the Genesis 1:1 walkthrough.