Comparing NT Syntax Searches

Dave Hooton
Dave Hooton MVP Posts: 35,776
edited November 21 in English Forum

I thought to compare OpenText and the new Lexham Syntax Graphs with a simplified Genitive Absolute search as below

 

The results are Lexham 123, OpenText 91.

Lexham has 4 additional verses (Mk 6:2; 6:22; Rom 8:11; 9:16) and OpenText has 1 additional verse at Mk 10:46. These are due to different analysis.

The additional results in Lexham are due to additional levels of the Subject structure which can be restricted to the "Last" in OpenText eg. Acts 15:2. How could I do this in the Lexham structure?

Dave
===

Windows 11 & Android 13

Tagged:

Comments

  • Rick Brannan (Logos)
    Rick Brannan (Logos) Member, Logos Employee Posts: 1,862

    The additional results in Lexham are due to additional levels of the Subject structure which can be restricted to the "Last" in OpenText eg. Acts 15:2. How could I do this in the Lexham structure?

    The Lexham Syntax Graphs bubble the lemma/morph/LN data for the head term up the graph, so the actual head term of each node has data available on each node. So technically, if you just want to find genitive absolutes (but not necessarily highlight the words that make them up) you don't even need the word node, you can specify case, mood, part-of-speech, lemma or LN data (article, subdomain, domain) at the node (here the "clause function") -- and not worry about the word object.

    This may not have fully made it to the version released with beta 4, and if it did it has errors in the head term and morph data. These have been corrected and I'm hoping the updated resource makes it into beta 5. But I just ran a search on Lexham Syntax Graphs (the corrected resource) and got 93 results. You'll likely get different results with your beta 4 version of the syntax database resource. A graphic of the query is below (first graphic). Note that I'm not saying this finds all genitive absolutes, I'm just trying to reconstruct what it seems you're doing.

    Further note: If you do want to highlight words, you could add a word object to each clause function that skips intervening levels. In future versions of the database, there will likely be a "word identifier" or something so you can specify agreement in "word identifier" between the node (here "clause function") and the word, to ensure you're highlighting the same thing. In the mean time, you can cheat by agreeing in LN Article because these are largely unduplicated in this type of context (this is the second graphic below; both queries have exactly the same hits, the second just highlights words). Also, I know there is inconsistent terminology in this dialog ("Head Text & Lemma" but "Term Morphology"); this will be clarified at a later date as well (likely not beta 5).

    image

    [second query, this one highlights the necessary words]

    image

    Rick Brannan
    Data Wrangler, Faithlife
    My books in print

  • Rick Brannan (Logos)
    Rick Brannan (Logos) Member, Logos Employee Posts: 1,862

    Looking for some more info on the genitive absolute so I could think about tweaking the search a bit, I see that titles of documents (including syntax searches) are also indexed, so the syntax search I made earlier popped up as a hit when I searched my library for "genitive absolute" (see below image). That'll be cool if I ever search for more info on genitive absolutes again -- and also a good reminder to have meaningful titles of user documents.

    image

    Rick Brannan
    Data Wrangler, Faithlife
    My books in print

  • Dave Hooton
    Dave Hooton MVP Posts: 35,776

    This may not have fully made it to the version released with beta 4,

    Thanks for the response Rick.

    Beta 4 does not have the Morphology at the Clause Function level, so I  will have to wait, slightly frustrated!

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,776

    the syntax search I made earlier popped up as a hit when I searched my library for "genitive absolute"

    Neat! I will rename my searches.

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,776

    This may not have fully made it to the version released with beta 4,

    Thanks for the response Rick.

    Beta 4 does not have the Morphology at the Clause Function level, so I  will have to wait, slightly frustrated!

    It did come with Beta 5 + Unordered Group. The OpenText results for Genitive Absolute match those of v3 and I didn't need a break to get them!

    image

    162 results

    image

    155 results = v3

    BUG: But the Search operation from the floating window does not work smoothly. It always opens a Syntax search pane but 2/3 times it is not run and cannot be got going from the Query window which seems to be stuck with the wrong version for "Today" i.e. the previous construct without Unordered Group.

     

    The numbers imply close results but it is misleading e.g. Syntax Graphs has 11 results in Revelation whilst OpenText has none. If you have some thoughts please share.

    [on Windows 7 RC, Athlon XP 2.16 GHz, 1.25 GB memory]

    Dave
    ===

    Windows 11 & Android 13

  • Cameron Watters (Faithlife)
    Cameron Watters (Faithlife) Member, Logos Employee Posts: 737

    BUG: But the Search operation from the floating window does not work smoothly. It always opens a Syntax search pane but 2/3 times it is not run and cannot be got going from the Query window which seems to be stuck with the wrong version for "Today" i.e. the previous construct without Unordered Group.

    The inconsistent result of clicking the "Search" button should be resolved in Beta 6 as I committed a fix for it on Tuesday.

    Director of Engineering for Enterprise and Operations

  • Dave Hooton
    Dave Hooton MVP Posts: 35,776

    The inconsistent result of clicking the "Search" button should be resolved in Beta 6 as I committed a fix for it on Tuesday.

    Excellent!

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,776

    The inconsistent result of clicking the "Search" button should be resolved in Beta 6 as I committed a fix for it on Tuesday.

    Thanks Cameron, it is more responsive and certain in Beta6.

    Dave
    ===

    Windows 11 & Android 13