CoreKnow What Each Tool Is For

Each tool answers a different question. Use the right one for the question you're asking.

  • Interlinear — English printed under each Greek word. Good for a quick orientation; poor as a daily reading habit (it reads the Greek for you).
  • Parsing tool — tells you the tense/voice/mood/case of a form. Identifies; does not interpret.
  • Analytical lexicon — lists every form in the NT and parses it. A look-up aid, not a meaning guide.
  • Lexicon — a true dictionary giving a word's range of meanings with citations (e.g., BDAG). This is where meaning is researched.
  • Grammar — explains syntax: how forms function in clauses (e.g., what a genitive can do).
  • Commentary — a scholar's interpretation of the passage, weighing grammar, context, and theology.
  • Bible software — packages many of the above together (Logos, Accordance, STEP Bible, Blue Letter Bible). Convenient — and convenient to misuse.

CoreWhy Strong’s Is Limited

Strong's Concordance numbers were created to index the King James Bible, not to function as a lexicon. A Strong's entry gives a short list of glosses — not a word's full range, not its usage by context, not its syntax. Relying on Strong's alone is how the root fallacy and lexicon shopping (see the fallacies page) usually happen.

A serious lexicon such as BDAG is a different kind of thing entirely: it organizes a word's meanings by sense, cites the passages that fall under each sense, and often tells you which sense applies to a given verse. That is research; a word list is not.

🔎 Strong's has a placeUse Strong's as an index — to find a word and look it up in a real lexicon. Just don't treat its gloss list as the meaning.

PracticeA Sound Workflow

Do the human work first; reach for tools in this order.

Recognize → parse → lexicon → syntax/context → commentary
  1. Try to recognize the form yourself. Read it before you click anything.
  2. Parse it — on your own if you can; with a parsing tool to confirm.
  3. Check a lexicon for the sense in this context (not just any gloss).
  4. Check syntax and context — how the clause works, what the paragraph is doing.
  5. Only then consult commentaries — to test and refine your reading, not to skip it.
⚠️ The limit of every toolTools can identify forms, but they cannot do exegesis for you. A parser names the tense; it cannot tell you what the author means. That work is yours.

CoreBad vs Better Tool Use

Three quick contrasts.

vocabulary
Example A — a word's meaning
Parse the key form(s)
Bad: open Strong's, see a gloss you like, and preach it.
Syntax
Better: use Strong's to find the word, then read the BDAG entry for the sense that fits this context, confirmed by the surrounding clause.
What the grammar contributes
The tool found the word; you (with a real lexicon and context) found the meaning.
What the grammar does not prove by itself
The gloss list alone proves nothing about this verse.
parsing
Example B — a verb's tense
Parse the key form(s)
Bad: a parser says “aorist,” so you announce the action was “once-for-all.”
Syntax
Better: note the aorist (perfective aspect), then read the context to see what kind of action is in view.
What the grammar contributes
The parser correctly identified the form; the interpretation came from context, not the label.
What the grammar does not prove by itself
The tense label does not carry the theological claim by itself.
syntax
Example C — a hard clause
Parse the key form(s)
Bad: jump straight to a commentary and copy its conclusion.
Syntax
Better: work the clause yourself (parse, syntax, context), form a tentative reading, then read the commentary to test it.
What the grammar contributes
The commentary sharpened a reading you had actually thought through.
What the grammar does not prove by itself
Outsourcing the thinking to a commentary teaches you little and risks misusing it.
⚖️ The governing principleGreek helps exegesis; it does not replace context, theology, or humility.
In summary
  • Each tool answers a different question — interlinear, parser, lexicon, grammar, commentary, software.
  • Strong's is an index, not a lexicon; BDAG-style lexicons research meaning by sense and context.
  • Workflow: recognize → parse → lexicon → syntax/context → commentary.
  • Tools identify forms; they cannot do exegesis for you.
  • Do the human work first, then let tools confirm and refine it.