For about 14 years, I have been talking to people about how important the Hebrew Scriptures (Old Testament) are for Christians to understand. With certain pastors, they have wanted to be Unhitched from the Old Testament. I’ve always said that nothing would be left if we removed sections of scripture that were related to the Old Testament.
Well, now that AI exists, I was able to build the Unhitched Bible. It shows you exactly how much would be removed if you submit every section (like the genealogy of Jesus in Matthew 1:17) to ChatGPI 3.5. If ChatGPT thinks it “referenced the Old Testament,” “quotes the O.T.” or “mentions someone from the O.T.” it is tag as “Not Unhitched.” I also took those sections of scripture and added subtitles based on how ChatGPT “saw” the scriptures.
As I am a WordPress developer, I felt that WordPress is the perfect platform to “hold” all of the data. I have a Custom Post Type called “ub_sections.” I couldn’t send every single verse one by one to ChatGPT because that would not be enough context to get an accurate idea of what just one verse is saying; therefore, I have broken it up into sections. Then I talked to the API at http://api.bible to pull the scriptures in the American Standard Version (because it is copyright-free) and stored all of the verses in JSON files. Next, it was time to import all of the verses into WordPress, creating the posts.
Once I had the titles (Matthew 1:1-17) and the verses imported, I wrote (using Cursor and AI) a script to take each post and send it off to ChatGPT 3.5 to assess the verses. I also told ChatGPT that it has to end each “AI Reasoning” with a tag of “Unhitched” or “Not Unhitched.”
I did not want to actually use WordPress for the front end. I figured it needed to be faster, and I didn’t want people to have to go page by page, clicking through the site. So the front end is a WordPress plugin I “wrote” using AI that uses React and the WordPress Rest API to pull in all of the content.
Feel free to go check it out at https://unhitchedbible.com/bible.