Ok, why? Give us a high level flow of your page... someone does a search against the bible table, the results are displayed, and the user is able to remove results they don't want?
So your idea is to store the results in a second table, then you could delete the results they didn't want from the second table? Who then clears out the results table? What happens if the user leaves the site? Your results table would explode in size..
Now, I assume you have no middleware, so your best option is to simply keep track of the IDs of the rows the user doesn't want, and include that in your SQL statement.