MétaCan
Menu
Back to cohort
Record W2898946804 · doi:10.1515/tlr-2018-2003

Split noun phrase topicalization in Eshkevarat Gilaki

2018· article· en· W2898946804 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueThe Linguistic Review · 2018
Typearticle
Languageen
FieldArts and Humanities
TopicSyntax, Semantics, Linguistic Variation
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsTopicalizationNumeral systemNoun phraseLinguisticsComputer scienceAntecedent (behavioral psychology)Determiner phraseSyntaxMovement (music)Base (topology)NounSubject (documents)Artificial intelligenceMathematicsPhilosophyPsychology

Abstract

fetched live from OpenAlex

Abstract Split noun phrase topicalization has been the subject of intense studies across languages in the syntactic literature of the last few decades. One of the key questions raised for these constructions is whether they involve syntactic movement or base-generation. This paper explores this phenomenon in two understudied Iranian languages, Gilaki (Northwestern Iranian, Caspien) and Persian. In particular, we explore splits in two contexts, possessive constructions and numeral constructions. We develop diagnostics for distinguishing the two derivational possibilities, movement or base-generation, for the cases under investigation. We show that while Gilaki uses both derivational possibilities, movement in possessor split and base-generation in numeral split, Persian only allows for the latter with very similar behavior. We argue that possessor split occurs when the whole possessum DP/DemP moves out of its base position in a small clause. Numeral split occurs when the NP is replaced by a null nominal element, which is associated with an overt or pragmatic antecedent. We end the paper with a discussion of why an operation, movement or base-generation, is available for one construction but not the other.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.006
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.966
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.006
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0030.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.049
GPT teacher head0.296
Teacher spread0.247 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it