torahverse.com

Torah, verse by verse

The Hebrew Bible is one of the most precisely addressed texts in the world: every sentence has a name. This page explains how the Tanakh is organized into books, chapters, and verses; how the weekly reading cycle divides the Torah across the year; how a citation like Genesis 1:1 works as a stable address; and how that address system lets a computer connect centuries of commentary to the exact verse each one discusses.

Books, chapters, verses: how the Tanakh is organized

Tanakh (תנ״ך) is the Hebrew acronym for the three parts of the Hebrew Bible: Torah ("teaching" — the Five Books of Moses, from Genesis through Deuteronomy), Nevi'im ("Prophets"), and Ketuvim ("Writings"). Counted the traditional way, the Tanakh contains twenty-four books.

The smallest unit is the verse, in Hebrew a pasuk (plural psukim) — roughly one sentence of text. Verse divisions are ancient: in the Masoretic manuscripts (the medieval manuscripts that fixed the standard Hebrew text, letter by letter), the end of each verse is marked with a sof pasuk ("end of verse"), a colon-like punctuation mark, and every word carries cantillation marks — the musical notation used for chanting the text aloud, which also functions as punctuation.

Chapters are much newer. The chapter divisions used today came from medieval Christian Bible scholarship, created for quick reference lookup, and later adopted into Jewish printed editions because a shared reference system is simply useful. This history explains why chapter and verse numbering can differ slightly between Hebrew editions and some Christian translations, and why traditional verse counts vary a little between Masoretic traditions.

The weekly parsha cycle

Alongside chapters, the Torah has an older and more practical division: the parsha (also called parashah or sidra; plural parshiyot) — the weekly Torah portion. The five books are divided into fifty-four portions, and one portion (occasionally two, combined to fit the calendar) is read publicly in synagogue each Shabbat, the Jewish Sabbath. Over the course of a year the whole Torah is read aloud from start to finish, and the cycle restarts each autumn on the holiday of Simchat Torah ("rejoicing of the Torah"), when the final verses of Deuteronomy and the opening verses of Genesis are read back to back.

Each portion is named after its first distinctive Hebrew word: the first portion is Bereshit ("In the beginning"), the second is Noach (Noah), the third is Lech Lecha ("Go forth"). The parsha names work like a second calendar — a week can be identified by its portion. Structurally, the parsha is a coarser addressing layer sitting above chapters and verses: the same text, sliced two different ways for two different purposes.

How a verse citation works

The standard citation convention is book chapter:verse. So Genesis 1:1 means the book of Genesis, first chapter, first verse — "In the beginning, God created the heavens and the earth." A range is written with a dash: Deuteronomy 6:4–9 names the six verses beginning with the Shema, the central declaration of Jewish faith, through the end of that passage.

reading a citationGenesis 1:1 → book (Genesis) · chapter (first) · verse (first). In Hebrew editions the numerals are written with Hebrew letters, which traditionally double as numbers — so the same verse is cited as Bereshit א:א.

The power of this convention is that the address is stable and universal. A commentator writing in medieval France, a scholar writing today, and a printed Bible on any shelf all point to the same words with the same short string. Nearly the entire library of Torah commentary — Rashi, Ramban, the Midrash, and thousands of later works — is keyed to verses: a comment exists about Genesis 1:1, or about Deuteronomy 6:4. The verse is the shared coordinate system of Jewish learning.

From address to database: making verses machine-readable

A stable address is exactly what a database needs. If every verse has one unambiguous name, then every verse can become a record — and everything written about that verse can be linked to it explicitly. The natural structure for this is a knowledge graph: a database made of nodes (things, such as a verse or a teaching) and edges (named connections between them, such as "this teaching cites that verse").

This is not hypothetical. The Torah graph at jew.tech — part of the same project as this site — anchors 33,323 verses as individual nodes, each carrying its Hebrew text and its address. Layered on top is a corpus of 17,147 cited teachings, every one stored with its Hebrew text, its source citation, and an embedding — a numeric fingerprint of meaning that lets a computer measure which texts are talking about similar ideas. Connecting the two layers are 15,910 teaching-to-verse citation edges: explicit links recording that a specific teaching discusses a specific verse.

Start from any verse and walk outward: every teaching in the corpus that cites it, then who taught it and what else they said. Or start from a teaching, walk back to its verse, then sideways to the other teachings anchored there. The centuries-old citation convention — book chapter:verse — turns out to be a ready-made schema. The Masoretic scribes who marked every sof pasuk were, in effect, building the index that makes this possible.

Part of a larger project

TorahVerse is one site in a network exploring the meeting point of Judaism and computer science. If the verse-level structure described here interests you, these are the places to go next:

jew.tech/torah-graph

The Torah knowledge graph itself — verses, teachings, sages, and the citation edges connecting them.

TorahChain

A companion site on the chain of Torah transmission — how teachings pass from teacher to student across generations.

TorahTwin

A companion site on building a faithful digital counterpart of Torah text and structure.

jew.tech

The hub of the network — the full project, its data, and its claims ledger.

Part of the Jew.tech network — Judaism and computer science, converging All sites · Discoveries · The builder