Asking original language questions in All (smart) search: intriguing finds

All search will automatically switch from smart to precise mode if you enter original language syntax such as "lemma.g:". However, it works as smart search if you do not use such syntax and yet use original language words. Note however the difference in the results and synopses between the search that uses greek and the one that uses transliterations:
This was a helpful discovery. It's logical but I had not realized the possibilities this offers.
The possibilities are also quite interesting in Bible Smart Search:
Comments
-
Other interesting use where smart searches approaches the precision of "precise" search but using natural language.
2 -
I have to explore the limitations (if someone has not done it yet) but here is another one that apparently worked, which is wow because the search is launched from the NASB:
2 -
@Francis These findings which you cite are wow! Thanks for sharing. I especially like the final one.
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
@Francis Try as I may, I can't get my data to display as yours has. Do I have a prioritization problem or have you employed some other method?
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
The data has to come from somewhere that you own. The main title I can think of that does that is the "Septuagint with Logos Morphology" which has the Greek tagged to the underlying Hebrew. Do you own it? Or perhaps it pulls from somewhere else, not sure. All I know is that it sure works for me.
1 -
Yes I do own it. Is there a way to exclude it from operating in this instance?
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
@Beloved Amodeo sorry, I misread your first post. Upon looking more carefully at your screenshot, you do have results but they show differently from mine indeed. Do you resources selected under "Add Versions"? If so, try removing them to see if that's causing it.
1 -
I had a dream there was a way to remove all additional references and it manifested. One need hover over any reference and a drop down popup appears, select remove all and one gets the desired results.
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
1 -
It seems that the results are not completely reliable though. First, for some reason, your results and mine have both verses in common and some that differ. Second, some of the results I got are not right.
As one post had mentioned early with regard to AI searches: if you can't verify visually from the result that it is correct, check it. In this case, this search does help me find relevant results but apparently includes false positives as well. So to be used with caution by those who know how to check.
0 -
It seems that the results are not completely reliable though
Your screenshot has chased instead of chesed. Changing that gives better results - though they still require checking
1 -
@Graham Criddle yes, I am aware of that, but thank you for pointing it out. I had input chesed but Logos suggested chased instead, so I tried it. However, I just tried again and it did not suggest it. Go figure. Looks like this specific type of search has interesting potential but can be a bit erratic. Upon further reflexion, it dawned on me that perhaps Logos' suggestion was not an alternate spelling for the Hebrew "chesed" but perhaps interpreting what I wrote as a mispelling of the English "chased" 😆. I was too immersed in original languages mode yesterday to notice that.
0 -
Thanks for sharing! From my German Einheitsübersetzung, I get similar but somewhat different results:
0 -
First, for some reason, your results and mine have both verses in common and some that differ. Second, some of the results I got I not right.
This is the nature of AI in most contexts as most AI exposed to the public is not exhaustive in its search nor predictable (to humans) in its paths.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
These results are not reliable nor comprehensive. The search warns you about this:
For this search, I'd strongly recommend using a precise search. It's not hard:
- Find an occurrence of this in the text. (Smart Search can help with this part!)
- Right-click the word, choose the Greek Lemma, then Copy Reference: Search
3. Paste that into a Precise Search query, then type
INTERSECTS
.4. Right-click again, choose the Hebrew lemma, then Copy Reference: Search
5. Paste that into your search query. You should have
lemma.g:ἀγαπάω INTERSECTS lemma.h:אהב
6. Set the search range to Logos LXX (or any LXX with a Hebrew reverse interlinear) and search:
You'll have a complete, accurate list of all Hebrew/Greek alignments between those two lemmas.
0