Peerapat Yangklang Assistant to the President Silpakorn University peerapat@ms.su.ac.th website |
Jordan Zlatev Division of Cognitive Semiotics Lund University jordan.zlatev@ling.lu.se website |
Participants: | 50 transcripts -- ages 4, 6, 9, 11, and 20 |
Type of Study: | narrative |
Location: | Thailand |
Media type: | no longer available |
DOI: | doi:10.21415/T5NK5Q |
If you publish any paper based on this data, please send an MS-Word or PDF-formatted version of your paper as an attachment to jordan_zlatev@ling.lu.se.
Zlatev, J. and Yangklang, P. (2001). Frog stories in Thai: Transcription and Analysis of 50 Thai narratives from 5 age groups. (forthcoming)
In accordance with TalkBank rules, any use of data from this corpus must be accompanied by the above reference.
Though our project focused on the development of spatial expressions in Thai, we made a serious effort to make the data as consistent and general as possible so that it could be used for other studies as well. We would also like to thank everyone who helped us carry out the collection and transcription of this data: Janich Feangfu, Maneeya Sangjan, Mingmit Sriprasit, Soraya Osathanonda, Martha Karrebaek Hentze and Katarina Lindblom.
The child data was collected in three Bangkok schools and the adult data was collected from students of Chulalongkorn University. The interviewer, always a native Thai speaker, first showed the Frog Story book to the subject and let him scan through it by himself for about 5 minutes. For the children, the instruction were approximately as follows: This story is about a boy, his dog, and a frog. I’ll let you take a look at the pictures of the story, first. Then, I will ask you to tell me the story, picture by picture.
The interviewer sometimes encouraged the child to proceed with the story. These utterances of the interviewer have not been transcribed. Even though we tried to keep the elicitation conditions as uniform as possible, there were inevitable differences due to the fact that five different interviewers collected the data. (The name of the interviewer appears first in the @Transcriber list.)
1.1.1 Transcription
Each recorded narrative was transcribed in standard Thai orthography, in almost all cases by the person, who performed the interview. The Thai transcription was then converted into a phonemic notation via the semi-automatic Thai Transcription program, developed at the Department of Linguistics, Chulalongkorn University. The consonants are as follows:
Table 1:
Thai Consonants
labial   | postdental   | palatal   | velar   | glottal |
---|---|---|---|---|
b | d | ? | ||
p | t | c | k | |
ph | th | ch | kh | |
f | s | h | ||
w | j | |||
m | n | N | ||
l | ||||
r |
Table 2: Thai Vowels
Front | Central | Back | |
---|---|---|---|
Close | i | U | u |
Mid | e | q | o |
Open | x | a | O |
Tones were marked as: Mid: 0, Low: 1, Falling: 2, High: 3, Rising: 4. Due to requirements of CHAT, the ? for glottal stop was omitted. The presence of the glottal stop is nevertheless derivable from the data since Thai syllables can not begin with a vowel or end with a short vowel. Whenever that seems to be the case in the data, there is an “invisible” glottal stop before the initial vowel or after the final short vowel.
1.1.2 Segmentation
Thai orthography does not place spaces between words: the space within the utterance corresponds to a hesitation pause. The transliteration program does not perform word seg-mentation either. Therefore, in order to allow the CLAN programs to perform automatic analyses (mlu, frequency counts etc.) the phonemic transcription needed to be segmented into words manually. This was straightforward in most cases since the vast majority of Thai words, especially in the colloquial register, are monosyllabic. However, it is not always clear if certain multi-syllabic expressions should be treated as (a) mono-morphemic words, (b) multi-morphemic words including lexical compounds or (c) phrases consisting of one or more words. In deciding how to analyze particular examples, we used the following criteria, disregarding diachronic evidence:
1. Mono-morphemic word IFF at least one of the syllables in the expression does not have a transparent separate meaning, e.g. naa2taaN1 (‘window’). Even though this expression is probably a compound diachronically, the compounding is not transparent for present-day speakers, so we decided to treat it as mono-morphemic.
2. Multi-morphemic word (“+” between the syllables) IFF all the syllables have transparent separate meanings, but the meaning of the whole is not derivable by combining that of the parts, e.g. phuu2+jaj1 (‘person’+‘big’ = ‘adult’). Lexical compounds are one subclass of this category. Derivations such as khwaam0+suk1 (PROPERTY + ‘happy’ = ‘happiness’) are also included in this category, even though their derivation is semantically regular.
3. Phrase (SPACE between the syllables) IFF the syllables have separate meaning, and combine systematically to give the meaning of the whole, e.g. maa4 (‘dog’) noj4 (‘little’) = ‘little dog’; raN4 (‘nest’) phUN2 (‘bee’) = ‘beehive’. In the same group as the second category, and thus marked in the same way (with a “+” connecting the parts) were expressions that appeared to be formulaic, e.g. may0+pen0+raj0 (‘never mind’). As for reduplications (cf. Luksaneeyanawin 1984), these were marked by connecting the parts with a double plus sign “++”, e.g. dek1++dek1 (‘children’). Using this notation compounds and other multi-morphemic words, formulaic expressions and reduplications can be treated as single lexical items (which is intuitively correct) by the CLAN programs, at the same time as analysis can easily be performed on their parts if required. For example, by adding the switch +b+ in the command line of the program MLU the constituent morphemes will be counted separately.
1.1.3 CHAT Formatting
The rough phonemic transcription was then checked against the original tape recordings and corrections were made. Deviations from standard pronunciation were included, using the convention offered by CHAT, placing the standard in square brackets behind pronounced form, e.g. laN0 [: raN0]. We then listened through the tape once more in order to mark all pauses: short (#) and long (##) and extra-long vowels, e.g. maa:4. Repetitions and re-tracings were marked using the CHAT conventions, i.e. the repeated material was surrounded by <> and followed by [/], [//] or [///].
Following the CHAT convention, each main line was made to include only one utterance – defined with a combination of phonetic and grammatical criteria. Thus, a line/utterance ends when both conditions are met:
The operational definition of a clause provided by Berman and Slobin (1994:660) (“a unit that contains … a predicate that expresses a single situation (activity, event, state). Predicates include finite and non-finite verbs, as well as predicative adjectives.”) could not be used since serial verb constructions, which are ubiquitous in Thai, can involve up to six verbs in what is arguably a representation of a “single situation”. While knowing that our decisions will not satisfy all scholars of Thai linguistics, we have tried hard to provide a clear set of criteria for identifying clause boundaries in the corpus, and by marking them with the conventional CHAT symbol [c], allow a first-order surface representation of grammatical complexity. According to our criteria [c] was used:
Given this way of marking clauses, we were faced with a dilemma as to how to satisfy the CHAT convention of having only one utterance per line (tier). If we chose only phonetic criteria, i.e. pauses and intonation contours, to define utterance boundaries, we would have to break up clauses – as previously defined – into many lines, and thus decrease readability and analyzability. On the other hand, if we neglected prosodic criteria and only segmented the text into clauses, we would miss the information that some clause boundaries coincided with pauses, and thus seemed to constitute processing units, while others did not. We resolved this dilemma with a compromise, operationally defining an “utterance”, i.e. the unit to be placed on a single line/tier, through a combination of phonetic and grammatical criteria:
U1. An utterance boundary (.) occurs when there is BOTH a phonetic indication of utterance closure – a short pause (#), a long pause (##) or a vowel lengthening (:) – AND a clause boundary, marked with [c].
This means that if there is only a pause but no clause boundary, then
the pause is marked within the utterance. If the utterance seems to
terminate without a clause being completed – the speaker “trails off” –
this is marked by ending the line with the symbol “+…” instead of the
utterance delimiter “.”. Likewise if there is a clause boundary, but no
pause of vowel lengthening, the utterance is assumed to continue until a
clause boundary and an utterance boundary coincide. An exception of the
condition U1 was made when there was only a single word (or short
phrase) serving as a “filler” between the clause boundary and the actual
pause, and in this case the utterance was terminated after this filler,
as in the following authentic example:
lxxw3 dek1 tUUn1 khUn2 maa0 #
phrOOm3 maa4 [c] lxxw3 # .
and child wake up come together dog and
‘And the child woke up, with the dog and.’
Finally, each of the 50 narratives was read though once again by at least two different checkers, correcting for any inconsistencies. Furthermore, a listing of all the words in the corpus was produced using the CLAN command freq +k *.cha +u +r6, and we went through this list word by word, making sure that each word is transcribed consistently throughout the corpus. In addition to standard CHAT codes, we used the %tai dependent tier for the Thai transcription and a double ++ to indicate reduplication as in “luuk2++luuk2.”
1.1.4 Files
The files are summarized in the following table. The subjects’ names do not appear in the transcripts.
Table 3: Thai Frog Files
File   | Age   | Sex   | Date |
---|---|---|---|
4a | 4;3.8 | f | 18-FEB-2000 |
4b | 3;11.20 | f | 18-FEB-2000 |
4c | 4;4.4 | f | 18-FEB-2000 |
4d | 3;10.12 | m | 18-FEB-2000 |
4e | 3;11.16 | f | 18-FEB-2000 |
4f | 4;0.2 | m | 8-SEP-2000 |
4g | 3;11.19 | f | 8-SEP-2000 |
4h | 3;6.15 | m | 8-SEP-2000 |
4i | 3;11.2 | m | 8-SEP-2000 |
4j | 3;11.22 | f | 8-SEP-2000 |
6a | 6;02.15 | m | 18-FEB-2000 |
6b | 5;11.23 | m | 18-FEB-2000 |
6c | 5;06.01 | m | 18-FEB-2000 |
6d | 5;06.11 | m | 18-FEB-2000 |
6e | 5;08.18 | f | 18-FEB-2000 |
6f | 6;04.1 | m | 18-FEB-2000 |
6g | 5;10.10 | f | 18-FEB-2000 |
6h | 5;06.25 | m | 18-FEB-2000 |
6i | 5;11.21 | m | 18-FEB-2000 |
6j | 6;01.17 | f | 16-FEB-2000 |
9a | 8;07.8 | m | 16-FEB-2000 |
9b | 9;0.21 | f | 16-FEB-2000 |
9c | 8;10.27 | m | 16-FEB-2000 |
9d | 9;0;11 | f | 16-FEB-2000 |
9e | 9;02.0 | m | 16-FEB-2000 |
9f | 9;03.2 | f | 16-FEB-2000 |
9g | 8;10.8 | m | 16-FEB-2000 |
9h | 8;07.0 | f | 16-FEB-2000 |
9i | 9;0.3 | f | 16-FEB-2000 |
9j | 9;07.2 | f | 2-FEB-2000 |
11a | 10;10.16 | f | 16-FEB-2000 |
11b | 10;05.22 | f | 16-FEB-2000 |
11c | 11;01.5 | f | 16-FEB-2000 |
11d | 11;04.2 | f | 16-FEB-2000 |
11e | 11;02.24 | m | 16-FEB-2000 |
11f | 10;08.27 | m | 16-FEB-2000 |
11g | 10;03.22 | m | 16-FEB-2000 |
11h | 11;0.16 | m | 16-FEB-2000 |
11i | 10;04.24 | f | 16-FEB-2000 |
11j | 11;03.18 | m | 16-FEB-2000 |
20a | 22;08.0 | f | 15-APR-2000 |
20b | 35;06.0 | f | 15-APR-2000 |
20c | 21;07.0 | f | 15-APR-2000 |
20d | 22;11.0 | f | 15-APR-2000 |
20e | 22;08.0 | f | 15-APR-2000 |
20f | 22;11.30 | m | 15-APR-2000 |
20g | 29;01.20 | m | 15-APR-2000 |
20h | 20;07.11 | m | 15-APR-2000 |
20i | 23;10.27 | m | 15-APR-2000 |
20j | 19;06.06 | m | 15-APR-2000 |
This data was collected as part of the First Language Acquisition of Thai project, funded by The Swedish Foundation for International Cooperation in Research and Higher Education (STINT) and hosted by the Department of Linguistics, Chulalongkorn, Thailand during 2000.