Yosef Shlomo Kahaneman
Israeli rabbi of the Litvishe Haredi tradition; re-installed Ponevezh Yeshiva in Bnei Brak
Yosef Shlomo Kahaneman (Hebrew: יוסף שלמה כהנמן; Yiddish: יוסף שלמה כהנעמאן; Lithuanian: Josifas Šleimė Kahanemanas, known also as the Ponevezher Rav), was an Orthodox rabbi and rosh yeshiva (dean) of the Ponevezh Yeshiva. He was also a member of the Council of Torah Sages of Agudath Israel.
Biography
Kahaneman was born 13 May 1886 in Kuliai, Kovno Governorate of the Russian Empire (present-day Lithuania), a town of about 300, of whom about a third were Jewish.
As a child he attended the yeshiva in Plungė led by Rabbi Chaim Yitzchak Bloch Hacohen. At the age of 14 he went to study Talmud at the Telshe yeshiva, where he studied Torah until he was twenty, under rabbis Eliezer Gordon and Shimon Shkop. He then spent half a year in Novardok yeshiva, after which he spent three years in Raduń Yeshiva studying under the Chofetz Chaim and Rabbi Naftoli Trop.
He married the daughter of the rabbi of Vidzh, and became rabbi there at the end of 1911, when his father-in-law became the rabbi of Vilkomir (Ukmergė). His nephew was Daniel Kahneman, a psychologist and economist.
After Rabbi Yitzhak Yaakov Rabinovich died in 1919 Kahaneman was appointed the new rabbi of Ponevezh. He built three yeshivas there, as well as a school and an orphanage.
The public source identifies “Yosef Shlomo Kahaneman” as israeli rabbi of the Litvishe Haredi tradition; re-installed Ponevezh Yeshiva in Bnei Brak. This brief keeps that definition visible, then builds a research path around Yosef, Shlomo and Kahaneman.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Yosef Shlomo Kahaneman”, the useful work is to connect “israeli rabbi of the Litvishe Haredi tradition; re-installed Ponevezh Yeshiva in Bnei Brak” to the records capable of establishing context and consequence.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jul 25, 2026. The linked authority identifier is Q2907349. VIAF identifies the subject as 97310299. The Library of Congress control number is no98086646. 4 of 4 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1886, 1911 and 1919.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Yosef Shlomo Kahaneman”, its source revision and the description used here.
- Expand the search: follow Yosef Shlomo Kahaneman primary sources, Yosef Shlomo Kahaneman archive and Yosef research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Yosef Shlomo Kahaneman”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Yosef Shlomo Kahaneman” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.