marking extraneous words as errors

19 views
Skip to first unread message

Daisuke Miyamoto

unread,
Feb 4, 2022, 6:52:19 AM2/4/22
to chibolts
Hello,

I would like to ask you whether it is possible to mark extraneous words as [: 0] [*]. For example, does the following transcription make sense?

*CHI:        there are a [: 0] [*] so many people living in the [: 0] [*] Japan .

By using [*], I intend to mark "a" and "the" as errors (incorrect use of a determiner). At the same time, I thought [: 0] can be used in order to exclude "a" and "the" from the %mor and %gra tiers. 

If this tagging does not seem to work, could you let me know if we have any other way to mark extraneous words as errors?

Best,
Daisuke Miyamoto
the University of Tokyo

Daisuke Miyamoto

unread,
Feb 4, 2022, 7:38:17 AM2/4/22
to chibolts
Hello again,

Sorry, CHECK let me know that using 0 inside [: ] is impossible.

***
[: ...] has to have real word, not 0... or &... or xxx.(158)
***

Thanks,
Daisuke

2022年2月4日金曜日 20:52:19 UTC+9 Daisuke Miyamoto:

Leonid Spektor

unread,
Feb 4, 2022, 9:27:08 AM2/4/22
to ChiBolts
Hi Daisuke,

I can not tell you if the following is conventionally correct, but it will pass CHECK and will work with CLAN commands. The following utterance will not put words "a" and "the" on %mor line:

*CHI: there are &-a [* extra] so many people living in &-the [* extra] Japan .

At the same time you can search for those word using FREQ with the following commands:

freq +s"[* extra]"
freq +s"[* extra]" +d6


Leonid.

--
You received this message because you are subscribed to the Google Groups "chibolts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chibolts+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/8c5e3e74-d419-4419-87f2-4c9544e388a3n%40googlegroups.com.

Brian Macwhinney

unread,
Feb 4, 2022, 9:33:41 AM2/4/22
to ChiBolts, Daisuke Miyamoto
Dear Daisuke,
I would treat the first of these two examples as a retrace. I would treat the second case as a semantic error involving the choice in English between the definite article, the indefinite article, and zero marking, as noted in section 18.1.2 of the manual. This coding isn’t quite right, but quite close. In general, if you need to track error types in very specific ways for your research, you could create additional fine-grained codes using methods as in that section.

*CHI: there are a [/] so many people living in the [* s:r:gc:art] Japan

Note that it is also possible the what you hear as “a” might have been the filled pause “uh” which we transcribe as &-uh. The fact that the verb is “are” rather than “is” argues for this interpretation.


— Brian MacWhinney
> --
> You received this message because you are subscribed to the Google Groups "chibolts" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to chibolts+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/9744e975-ee75-4f4c-8d68-34d9dd4671e5n%40googlegroups.com.

Daisuke Miyamoto

unread,
Feb 4, 2022, 10:05:24 AM2/4/22
to chibolts
Hi Leonid and MacWhinney,

Thank you for your prompt responses! Using "&" or a retracing marker sounds fine. I originally thought that [: text] (or [:: text]) is necessary when we use [*], but now I understand this is not always the case.  I'm going to learn how to code specific error types more.

Best,
Daisuke Miyamoto 

2022年2月4日金曜日 23:33:41 UTC+9 macw:
Reply all
Reply to author
Forward
0 new messages