Lexicography

The “Annoying Little Words” & Exegesis – An Interpretive Lexicon

This is the second post out of two (see the first here) describing my recent, co-authored publication An Interpretive Lexicon of New Testament Greek (here). In the first I described the “interpretive” and “lexicon” aspects of the book. Here I want to focus on what I think is the best feature of it, and why it’s an exegetical golden goose. Let me preface much of this by saying that our “Introduction” in the Lexicon covers more detailed material that will also be helpful.

This post is a bit technical and won’t have many pictures, so strap on your thinking cap.

The Significance of the “Annoying Little Words”

I began to talk about function words in the first post. These are the words that students usually think of as quite annoying. For the most part, that is correct, since these words rarely have a neat definition that can be slapped on the back of a flashcard. The reason is that their whole raison d’être is to connect larger ideas (typically clauses but also paragraphs and other larger units of text). This basically means that the annoying little words are “multivalent” or “polysemous”. That is to say, they often take one of two or more possible meanings, depending on their context. And of course, since they are “function” words after all, the meaning they take in context will greatly affect what they doOkay, so that was abstract. Let’s get textual. Look at the fancy graphic above that I made. It shows a ‘cloud’ of the most frequently used words in the book of Romans. Notice how the obvious candidates like χάρις (‘grace’) or δικαιοσύνη (‘righteousness’) or νόμος (‘law’) are not immediately visible. The most prominent words are … you guessed it, the annoying little words. You get a gigantic καί and a δέ, a γάρ, a few definite article forms, and a few prepositions (διά, εἰς, ἐν). In fact, the one and only content word that is fairly visible is the genitive form of θεός (‘of God’).

My point is that you can only get to the “big ideas” of a book like Romans – or any text – by first going through the little words. They are absolutely indispensable to communication, slippery as they are to pin down to a single definition. Fortunately, we use function words automatically in our everyday speech and never give it a second thought. Unfortunately, this can make it all too easy to overlook their incredible importance in the task of interpretation.

Discourse Analysis

An English Example

To do some of the heavy lifting of dealing with function words in interpretation, some undertake a process that many call ‘discourse analysis,’ although it goes by other names as well (e.g. ‘text linguistics’). What this process aims to do is discern the larger structures and connectedness of a text. Remember that function words are sometimes called “connecting” words. They connect two (or more) larger chunks of text. As a result, if you want to determine the connection between Thought ‘A’ and Thought ‘B’ then you need to understand the function words that relate them.

Take the previous sentence for instance. It is made up of two main clauses:

1) you want to determine

and

2) you need to understand

Somehow, the two actions – 1. determining and 2. understanding – are related logically in that sentence. And the way they are related is by the two function words if and then. The first clause (wanting to determine) is conditional upon the second clause (needing to understand). This may seem obvious, but the point is that the words ‘if’ and ‘then’ manifest the conditional relationship between these two clauses, and therefore help the reader or listener ‘exegete’ this bit of communication.

But there is another important part of that sentence: The very first part, “As a result ” What we have here is a phrase – a syntactical construction – that serves as a road sign to the logic of the larger text. Linguists sometimes call this a ‘discourse marker’ (among other things). What the ‘as a result‘ phrase does is link that sentence to the one that precedes it logically. In essence, the idea is “A is such, therefore B is such.” The ‘B’ aspect is a result of the A aspect.

Getting Greeky

Let’s have a look at Romans 11:23:

And they also, if they do not continue in their unbelief, will be grafted in; for God is able to graft them in again” (NASB).

κἀκεῖνοι δέ, ἐὰν μὴ ἐπιμένωσιν τῇ ἀπιστίᾳ, ἐγκεντρισθήσονται· δυνατὸς γάρ ἐστιν ὁ θεὸς πάλιν ἐγκεντρίσαι αὐτούς.

I have boldfaced the (main) function words in the sentence. Note that the first one, ‘and’ is a conjunction that ties this sentence to the one that precedes as a coordinate idea. Then there is a(n implicit) conditional clause with the ‘if’ statement, so that the notion is ‘if they do not continue in their unbelief, then they will be grafted in.’ Finally, the rationale that grounds this statement is provided in the next clause and introduced by the word for: “for God is able …”

The Logical Main Point

All of this may seem pedantic. But there is a payoff. Language has what scholars call ‘semantic structure.’ That is to say, there is an ‘architecture,’ to so speak, of any communication (written or otherwise) that makes it understandable. As with a building, a well-constructed piece of writing or speech has a solid frame. Instead of steel beams, however, language uses what we might call semantic logic. It is important to realize that the presence of function words like ‘because’ or ‘therefore’ does not produce logical structure, but manifests it. In other words, the connecting words are there because language has semantic structure, not the other way around.

Here’s proof. In the Rom. 11:23 example above I mentioned that there was an implicit conditional clause. That is because the “second half” of a conditional – the word then – does not actually appear in the text. It is implied. And yet as readers or hearers the conditional sense is understood nevertheless. This applies to other logical relationships as well. For example, I can say “I’m not going outside. It’s cold” and you understand perfectly that the second statement is the reason for the first, and could be connected by the word because for the same effect. The logical structure is there whether or not the words are there to point to them. (Also note that one could not put a ‘therefore’ between those two clauses without producing nonsense; only some logical relationships are possible in a given context).

The Interpretive of the Lexicon (Again)

Bringing this all the way back around to the Interpretive Lexicon, as I alluded to in my first post, we use a system of letters and symbols to key the reader into the logical relationship – the discourse-level function – of the word being discussed. Again, these words are often multivalent and can be taken in several ways depending on context. That is where our lexicon comes in, to help the reader swiftly narrow down the possible logical relationships of a word (or phrase) in Greek, and therefore to better (and more quickly) understand the text.

To conclude, here is the set of our relationships included in the Lexicon. We also include an extended section carefully defining each one and providing an example. We have also aligned our own logical relationships with those used at John Piper’s online site BibleArc.com in order to maximize their compatibility. It is our great hope that it can be used to help pastors, students, and scholars as well as each one reads and interprets the Greek scriptures.

abbrev

G. K. Beale, Daniel J. Brendsel, and William A. Ross, An Interpretive Lexicon of New Testament Greek (Zondervan, 2014), 23.

 

 

 

 

 

Upcoming Presentations at ETS & SBL ’14 – San Diego

Balboa Park, San Diego. Museum of Man pictured right.

One of the things I have been trying to do over the past year and a half or so is to attend and participate in more biblical studies conferences. Some of this I have written about previously (here). It’s a lot of fun, if occasionally overwhelming and often expensive. But it’s also worthwhile. I’m working on a post right now for aspiring doctoral students of biblical studies that will be a kind of “how-to” (and a “why”) for the conference scene, which can be tremendously beneficial to the student. So look for that in a few weeks.

SBL National Conference

The upcoming annual Society of Biblical Literature (SBL) conference will be held from November 22nd-25th in San Diego, CA. The location will be a welcome change compared to the prior two years’ frigid locales, Baltimore and Chicago, respectively. Information about the meeting, including registration, transportation, and housing are on the annual meeting page.

Rumor has it the book exhibit will be on the beach.

I am excited to have the opportunity to participate by presenting a paper this year. I will read it at the IOSCS program unit (here), which usually meets at least twice during the conference. My paper will be an extension of the research I presented at the 2013 IOSOT Congress in Munich, which dealt with Septuagint lexicography in the double-text of LXX-Judges.

In the congress paper I took a brief foray into verifying research done almost fifty years ago now by John A. L. Lee in LXX lexicography. Lee’s work was decisive in demonstrating that LXX Greek is in fact simply the vernacular Koine of its time, not a special “Jewish Greek” that some scholars had posited (for more on the language of LXX, see this post). Lee also dipped into historical linguistics using documentary evidence to establish a terminus ante quem for the translation of the Greek Pentateuch. His dissertation is in print (and quite affordable, here). An abstract of my previous congress paper and its appendix are available here.

My SBL presentation will focus again on LXX lexicography and the Greek texts of Judges. This time I will be considering the translational renderings of the prevalent battle language throughout the book. Words like לחם and  מלחמה are translated in interestingly divergent ways in the A text as opposed to the B text. The question I will be asking then is simply, “Hmm… why?” I don’t have a clear answer yet! But I have my suspicions. Lee’s methodology of lexical inquiry in documentary evidence will be a primary avenue of inquiry for this paper (using papyri.info, which I have reviewed in part here). Hopefully come November I will have something cogent to offer in terms of an answer.

A full abstract is available here.

ETS National Conference

I will also participate in the ETS conference, also held in San Diego just prior to SBL, presenting a paper in the Psalms & Hebrew Poetry section. I have not been as active in ETS as I have in SBL in the past few years, so I’m looking forward to being a part of this conference. Although it’s a smaller event by far, it is still a great way to see what is happening academically within the purview of evangelicalism. 

My paper is a product of a longer study I did a few years ago in Nahum 1 (here and here). I presented a paper at a regional ETS a year ago that was less extensive (and sparsely attended!), so I’m looking forward to presenting this more in-depth analysis. 

The basic issue at hand is the question of the presence (or absence) of an acrostic in chapter 1. Especially in vv. 2-8 there is what appears as a partial, or “broken,” acrostic spanning the first half of the alep-bet. Ever since F. Delitsch mentioned it in his Psalms commentary there have been innumerable attempts to reconstruct it to either a full acrostic (older commentators mostly), or a complete half-acrostic (most current approaches). Although some are content to take the text as is, either as a coincidence or literary device, the majority opinion still leans towards textual emendation, to the extent that even BHS lays out the verses as an acrostic. 

My paper considers the warrant for emending the Hebrew text on the basis of a translation analysis of the Greek version, which is ordinarily the primary witness to which those who would emend the text appeal. Without giving too much away, my paper is entitled “There is No Spoon: Text-Critical Question Begging in the ‘Acrostic’ of Nahum 1 .” An abstract is available here.

A User’s Guide to Papyri.info (Part II) – Text

I’ve said it before, but I repeat. Papyri.info is an amazing resource. In preparation to provide a Resource Review for it, I ended up writing a primer post (here). Now, I should say up front that Papyri.info is useful for a very specific niche within LXX research, and that is lexicography. So if you are not interested in lexicography, you can probably skip this review. Otherwise, read on.

To reiterate a point from my primer post, there is debate still going on as to whether the meaning of the Greek words in the LXX are to be determined primarily by reference to their Hebrew counterpart in the source text, or primarily by reference to their contemporary Hellenistic usage.

Eleazar Killing a War Elephant in the Maccabean War (1 Macc. 6:42-47), by B. Picart Broen, 1728

Generally speaking, the debate is not a neat either/or matter, but rather one of primacy. There are many good reasons to take the Hebrew parent text as primary in a number of cases. These tend to be words that have become a terminus technicus. Still, although a Greek word may come to mean something more or different than it did prior to its use in the LXX (e.g. διαθήκη, εἰρήνη), this is not particularly unique. Lexicographers have recognized for some time that word meaning is not static. What this amounts to, then, is that the new uses of Koine words in the LXX is not necessarily due to its status as a translated text. It may rather be attributable to the new socio-political-(religious) context(s).

So, as promised, I shall punt on this issue (for now), and press on.

Background to Papyri.info

As discussed on the homepage, this LXX resource consists of the papyrological navigator and the papyrological editor. Since I have no business dealing with the latter, I won’t (most likely, neither should you). The former, however, “supports searching, browsing, and aggregation of ancient papyrological documents and related materials.” The wonderful thing about papyri.info is that it is a one-stop resource for material that quite recently was scattered hither and yon. As the homepage says, the site collates material from the Advanced Papyrological Information System (APIS), Duke Databank of Documentary Papyri (DDbDP), Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV), Bibliographie Papyrologique (BP). 

Most of this information was accessible by CD-Rom prior to the mid-2000s, but now it’s all free and constantly updated. To force you to appreciate how wonderful this is, consider this quote:

“Not just hours or weeks, but months were spent searching for [Greek] words in the indexes of documentary volumes and confirming occurrences. Every text had to be laboriously copied by hand in the library, then recopied into the manuscript when written, before finally being handed over for typing… Photocopying was only just beginning to be possible” (J. A. L. Lee, “A Lexical Study Thirty Years On,” 515).

 So count yourself lucky to be a part of the age of xerox, email, and open-source internet. The “how-to” I’ve written up below walks through some material laid out on the papyri.info site already, and some of my own additions as well.

Using Papyri.info

Considering that this is a freely accessible website, the functionality of papyri.info/search is remarkable. The first thing you’ll notice is the main search window:

search

I will usually tick the “Convert from betacode as you type” button so that your keystrokes enter Greek directly. Otherwise, you have to cut-and-paste unicode Greek font from somewhere else. A good guide to betacode typing can be found here (also pdf). The other toggle buttons are self-evident: if capitalization is relevant to your search (e.g. proper nouns), you may want to un-tick “Ignore Capitalization,” and the same for diacritics/accents.

The most simple type of search is a “string” search, meaning “string” of characters. Simply entering καί into the search bar, for example, will turn up 31,604 hits. Note how the site conveniently highlights your word(s) when you click on a particular text. Moreover, you can link to that text and have the highlighting remain (see p.worp 16, below). But back to the search on καί. It is important to know that included in the massive search result number is any word in which the characters κ-α-ί occur in sequence, such as καῖσαρ or καιρός. This is where the ‘#’ code is crucial, as it breaks off a string from surrounding characters. If you wanted only καί, then, you would enter #καί#, which would return 28,138 hits.  

Further, you can search for phrases using quotes. So if you were looking for instances of μὴ φοβοῦ, you’d enter “‘μὴ φοβοῦ'” and get just a single hit (p.worp 16). You’ll notice that in p.worp 16 there is a translation of the papyrus provided. This is a major boon when it happens, although in my experience that is rarely. Of course, in this case, the translation is into Italian, but it is helpful nevertheless.

You’ll also notice the group of buttons below the search bar. buttonsThese buttons really amplify the capacity of the engine, so they’re worth learning to use. I will spend some time walking through the more basic button functions here, and then wait until a third (!) post to treat the more sophisticated ones… partly because I’m still figuring them out.

Firstly, the “and” “or” and “not” buttons do exactly what you would expect. When you enter any Greek word in the search window, then hit one of those three buttons, a second search window will appear below for your second criterion (or third, etc.).comboThis allows you to include, alternate, or exclude certain words.

The following two buttons, “then” and “near,” deal more with sequencing of words. For example, if we wanted to see if the prepositional phrase εἰς ἀπάντησιν occurs in any papyri, we’d type, εἰς and click the “then” button and add ἀπάντησιν. The “within ___” window will become active automatically, and we’ll enter 3, for example, and then select “words” from the drop-down to the right, although you can also search by character for more refined quests. So our sample search is “εἰς THEN ἀπάντησιν within 3 words.” We get two results:

Eureka!

Eureka!

Note that the “then” button sets up the search for terms in the order in which they were entered (εἰς followed by ἀπάντησιν), while the “near” button searches in either direction within the limits you set, whether by word or character.

This is one of innumerable possible searches just with these first few buttons. As mentioned, I will reserve comment on the following buttons for a third installment. The last few are the most powerful (and finicky), and so take space to treat well. Disclaimer: It may take me some time to produce this final post.