This document provides an overview of annotation conventions for proper nouns used in Oracc. We focus here on the data-entry view of linguistic annotation giving only enough additional technical background to ensure that correct annotation of ATF files can be carried out.
This document assumes knowledge of the introductory page on Oraccc linguistic annotation.
{m}ha-am-mu-ra-bi
not {d}Ha-am-mu-ra-bi
.{f}la-ma-as-sa-ni
.{d}a-nu--ŠEŠ-šu--DIN
= Anu-ahšu-uballiṭ). However, new projects are encouraged not to use double hyphenation.Most lemmatization of proper nouns follows the conventions of the relevant language; here is a summary of the conventions common to all proper nouns. For further language-specific information, see the pages on Akkadian, Aramaic, Elamite, Greek, Old Persian, and Sumerian.
This page describes explicit lemmatization. See the page on Linguistic Annotation for the difference between explicit and POS-only lemmatization of proper nouns.
{f}la-ma-as-sa-ni = +Lamassani[]PN$
.{m}{d}60-EN-šu-nu = +Anu-belšunu[]PN$
and {m}ri-mut-{d}60 = +Rimut-Anu[]PN$
.Anu-bēlšunu
or Rīmūt-Anu
).Partially broken proper nouns should be lemmatised wherever possible, according to the following conventions:
X
. For instance, {m}x = +X[]PN$
.X
. For instance, {m}[...] = +X[]PN$
.{d}EN-[...] = +Bel-X[]PN$
and x-x-u₂-bal-liṭ = +X-uballiṭ[]PN$
.{d}a-nu-$U₂-[...] = +Anu-U₂.X[]PN$
it is possible that the U₂
might be read šam
instead of u₂
.There are three types of GW for proper nouns:
+Purattu[Euphrates]WN$
.+Nidintu-Anu[01]PN$
is a different person to +Nidintu-Anu[02]PN$
. Make sure to apply these numerical codings consistently across your corpus, so that it is always the same Nidintu-Anu who is assigned GW [01]
. This will ensure that the glossary treats them as separate individuals.+Ištar[]DN$
does not need a numerical or modern-language GW if she is written "Ištar" in the translation and there is only one deity of that name.SENSEs are rarely used in lemmatising proper nouns.
POS tags for proper nouns are not language-specific. In the table below,
the Class
column indicates how the different NN types are
grouped in glossaries.
POS | Meaning | Class | Pseud-lang |
---|---|---|---|
AN | Agricultural (locus) Name | Places | qpn-x-people |
CN | Celestial Name | Celestial | qpn-x-celest |
DN | Divine Name | Divine | qpn-x-divine |
EN | Ethnos Name | Ethnic | qpn-x-ethnic |
FN | Field Name | Places | qpn-x-places |
GN | Geographical Name (lands and other geographical entities without their own tag) | Places | qpn-x-places |
LN | Line Name (ancestral clan) | People | qpn-x-people |
MN | Month Name | Month | qpn-x-months |
ON | Object Name | Object | qpn-x-object |
PN | Personal Name | People | qpn-x-people |
QN | Quarter Name (city area) | Places | qpn-x-places |
RN | Royal Name | People | qpn-x-people |
SN | Settlement Name | Places | qpn-x-places |
TN | Temple Name | Temples | qpn-x-temple |
WN | Watercourse Name | Watercourses | qpn-x-waters |
YN | Year Name | Year name | qpn-x-ynames |
EPOS is helpful in cases where, for instance, royal names are deified or celestial entities are named after deities. For example:
4. {mul}GU.LA u {d}ŠUL.GI #lem: +Gula[]DN'CN$; u[and]CNJ; +Šulgi[]RN'DN$
It is only necessary to add a NORM0 to the lemmatisation if the spelling shows a morphological difference from the CF. For instance, ak-ka-di-i = +Akkadu[Akkadian]EN$Akkadi
.
Ideally, your translation of a proper noun should match either the modern-language GW (see above) or the CF, with short vowels, if the GW is empty or numerical.
18 Dec 2019Eleanor Robson & Steve Tinney
Eleanor Robson & Steve Tinney, 'QPN: Oracc Linguistic Annotation for Proper Nouns', Oracc: The Open Richly Annotated Cuneiform Corpus, Oracc, 2019 [http://oracc.museum.upenn.edu/doc/help/languages/propernouns/]