Bible Corpus
English Bible Translations Dataset for Text Mining and NLP
@kaggle.oswinrh_bible
English Bible Translations Dataset for Text Mining and NLP
@kaggle.oswinrh_bible
Bible (or Biblia in Greek) is a collection of sacred texts or scriptures that Jews and Christians consider to be a product of divine inspiration and a record of the relationship between God and humans (Wiki). And for data mining purpose, we could do many things using Bible scriptures as for NLP, Classification, Sentiment Analysis and other particular topics between Data Science and Theology perspective.
Here you will find the following bible versions in sql, sqlite, xml, csv, and json format:
American Standard-ASV1901 (ASV)
Bible in Basic English (BBE)
Darby English Bible (DARBY)
King James Version (KJV)
Webster's Bible (WBT)
World English Bible (WEB)
Young's Literal Translation (YLT)
Each verse is accessed by a unique key, the combination of the BOOK+CHAPTER+VERSE id.
Example:
Genesis 1:1 (Genesis chapter 1, verse 1) = 01001001 (01 001 001)
Exodus 2:3 (Exodus chapter 2, verse 3) = 02002003 (02 002 003)
The verse-id system is used for faster, simplified queries.
For instance: 01001001 - 02001005 would capture all verses between Genesis 1:1 through Exodus 1:5.
Written simply:
SELECT * FROM bible.t_asv WHERE id BETWEEN 01001001 AND 02001005
Coordinating Tables
There is also a number-to-book key (key_english table), a cross-reference list (cross_reference table), and a bible key containing meta information about the included translations (bible_version_key table). See below SQL table layout. These tables work together providing you a great basis for a bible-reading and cross-referencing app. In addition, each book is marked with a particular genre, mapping in the number-to-genre key (key_genre_english table) and common abbreviations for each book can be looked up in the abbreviations list (key_abbreviations_english table).
While its expected that your programs would use the verse-id system, book #, chapter #, and verse # columns have been included in the bible versions tables.
A Valuable Cross-Reference Table
A very special and valuable addition to these databases is the extensive cross-reference table. It was created from the project at http://www.openbible.info/labs/cross-references/. See .txt version included from http://www.openbible.info website. Its extremely useful in bible study for discovering related scriptures. For any given verse, you simply query vid (verse id), and a list of rows will be returned. Each of those rows has a rank (r) for relevance, start-verse (sv), and end verse (ev) if there is one.
Basic Web Interaction
The web folder contains two php files. Edit the first few lines of index.php to match your server's settings. Place these in a folder on your webserver.
The references search box can be multiple comma separated values. (i.e. John 3:16, Rom 3:23, 1 Jn 1:9, Romans 10:9-10) You can also directly link to a verse by altering the URI: [http://localhost/index.php?b=John 3:16, Rom 3:23, 1 Jn 1:9, Romans 10:9-10](http://localhost/index.php?b=John 3:16, Rom 3:23, 1 Jn 1:9, Romans 10:9-10)
In CSV folder, you will find (same list order with the other formats):
In behalf of the original contributors (Github)
WordNet as an additional semantic resource for NLP
CREATE TABLE bible_version_key (
"id" BIGINT,
"table" VARCHAR,
"abbreviation" VARCHAR,
"language" VARCHAR,
"version" VARCHAR,
"info_text" VARCHAR,
"info_url" VARCHAR,
"publisher" VARCHAR,
"copyright" VARCHAR,
"copyright_info" VARCHAR
);CREATE TABLE key_abbreviations_english (
"id" BIGINT,
"a" VARCHAR,
"b" BIGINT,
"p" BIGINT
);CREATE TABLE key_english (
"b" BIGINT,
"n" VARCHAR,
"t" VARCHAR,
"g" BIGINT
);CREATE TABLE key_genre_english (
"g" BIGINT,
"n" VARCHAR
);CREATE TABLE t_asv (
"id" BIGINT,
"b" BIGINT,
"c" BIGINT,
"v" BIGINT,
"t" VARCHAR
);CREATE TABLE t_bbe (
"id" BIGINT,
"b" BIGINT,
"c" BIGINT,
"v" BIGINT,
"t" VARCHAR
);CREATE TABLE t_kjv (
"id" BIGINT,
"b" BIGINT,
"c" BIGINT,
"v" BIGINT,
"t" VARCHAR
);CREATE TABLE t_wbt (
"id" BIGINT,
"b" BIGINT,
"c" BIGINT,
"v" BIGINT,
"t" VARCHAR
);CREATE TABLE t_web (
"id" BIGINT,
"b" BIGINT,
"c" BIGINT,
"v" BIGINT,
"t" VARCHAR
);CREATE TABLE t_ylt (
"id" BIGINT,
"b" BIGINT,
"c" BIGINT,
"v" BIGINT,
"t" VARCHAR
);Anyone who has the link will be able to view this.