Main content



Loading wiki pages...

Wiki Version:
This repository contains files related to the paper "Range in the use and realization of *BIN* in African American English" accepted by *[Language & Speech](* in June 2022. The paper builds on: - some of the work presented in our [talk]( at [NWAV 48]( in October 2019. - [Neal et al. (2020)'s]( NWAV 48 proceedings paper, which provides some additional analysis of the effect of context in the experiment. We are grateful for funding for this project from: - UMass Faculty Research Grant/Healey Endowment Grant - UMass Institute of Diversity Sciences Seed Grant - National Science Foundation, Linguistics Program, BCS Award [2042939]( (Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.) There are files for two different studies conducted: 1. [Corpus of Regional African American Language (CORAAL)]( "been" search and analysis 2. Production study in a small town in southwestern Louisiana (SWLAT) --- ## CORAAL files - `OSF_CORAAL_Appendix.docx` contains a little more information about how the [CORAAL Explorer]( interface was used for the 'been' search. - `OSF_CORAAL_search_results.xlsx` contains a spreadsheet of the CORAAL 'been' examples collected and analyzed. - The `stressed_been` worksheet contains the 20 *BIN* examples found. The `Predicate` column specifies the type of predicate that follows the *been*, and `Full Predicate` lists the entire predicate of the utterance. The `PreModal` and `ModalType` columns contain information about the type of modal preceding the *been*. `OvertHave` refers to whether there is an overt *have* (indicated by `1`) or not (indicated with `0`). Columns `Adverb1` and `Adverb2` list more information about the surrounding adverbs. - The `perfect + advb` worksheet contains instances of perfective been followed by an adverbial phrase. The `BIN compatible` column indicates if the utterance is compatible with the semantics of BIN (`CMP`:compatible; `INCMP`:incompatible). The column `Adverb (In)compatibility Type` specifies the type of adverb. - The `done been` worksheet contains 5 instances of the *done been* construction. These are also listed in the previous worksheetm but have been pulled for ease. - The `incompatible` worksheet contains the remaining instances of the *been* search. ## SWLAT files 1. `OSF_swla_items_hash.xlsx` 2. `OSF_swla_slides_ordered_by_condition.pptx` 3. `OSF_perceptual_judgment_analysis_swla.pdf` 4. `OSF_phonetic_analysis_swla.pdf` ### `OSF_swla_items_hash.xlsx` This spreadsheet lists the items elicited in the SWLAT production study. The fillers are listed at the end. The columns in the spreadsheet are: - **item**: item code - **target.word**: target word (immediately following BIN/been) - **target.stress**: stress on target word (initial, final, monosyllabic) - **BIN_pos**: part of speech for BIN construction (verb, PP) - **condition**: BIN/been type - `_rs`: BIN_complete (BIN_comp) - `_state` BIN_state_continuous (BIN_state_cont) - `_habitual` BIN_state_habitual (BIN _state_habit) - `_epiPerf`: been ppart (past participle been) - `modal-could`: modal BIN construction, using *could*, i.e, BIN could - `modal-supposed` modal BIN construction, using *supposed to*, i.e., BIN was supposed to - `habitual-adv`: BIN construction followed by long time adverbial, e.g., "for a long time", "for a while" - **filler_type**: note about construction type for filler - **context**: text of context auditorily presented for elicitation of item - **target**: written prompt (and spoken utterance) elicited - **wordcount_context**: number of words in context - **wordcount_target**: number of words in target ### `OSF_swla_slides_ordered_by_condition.pptx` These are the slides (with auditory contexts and illustrations and written prompts) that were used to elicit utterances in the SWLAT production study. The illustrations were created by the artist [Sachio Cook]( The slides are ordered by BIN/been type condition, you can see the item code if you click on `View > Outline View` in PowerPoint. The slide titles are the item codes. The audio is embedded and so should be playable. The first few slides show instructions and familiarization (practice) items. In the slide title (item code), the BIN/been type condition codes are given as suffixes, following the target word, e.g., `align_habitual` was the item corresponding to target word "align" and BIN/been type "habitual": - `_rs`: BIN_complete (BIN_comp) - `_state` BIN_state_continuous (BIN_state_cont) - `_habitual` BIN_state_habitual (BIN _state_habit) - `_epiPerf`: been ppart (past participle been), - ... etc., see explanation of **condition** for `OSF_swla_items_hash.xlsx` ## Statistical analysis files The files used in statistical analysis are included in the directory `statistical_analysis/`, which as two sub-directories: 1. `perceptual_labels/`: files related to Sections 3.2.1 through 3.2.3 in the paper 2. `phonetic_analysis/`: files related to Section 3.2.4 in the paper Within these two sub-directories there are the following files and sub-directories: 1. `.Rmd` file: this is the R notebook code 2. `.html` file: this is the compiled output of the R notebook code, which can be viewed in a web browser. 3. `data/`: this sub-directory contains data files that are read into the environment in the R notebook 4. `figure/`: this sub-directory contains the figures produced by the R notebook 5. `out/`: this sub-directory is only in the `perceptual_labels/` directory and contains data frames written to file (this output is then used as input for the R notebook in `phonetic_analysis/` and included in the `data/` sub-directory in `phonetic_analysis/`. ## Example fundamental frequency contour figures The compressed file `` contains the various files used to create the example fundamental frequency contour from CORAAL and the SWLAT task through out the paper. Each figure has its own sub-directory.
OSF does not support the use of Internet Explorer. For optimal performance, please switch to another browser.
This website relies on cookies to help provide a better user experience. By clicking Accept or continuing to use the site, you agree. For more information, see our Privacy Policy and information on cookie use.

Start managing your projects on the OSF today.

Free and easy to use, the Open Science Framework supports the entire research lifecycle: planning, execution, reporting, archiving, and discovery.