Contrastive Analysis of Imperative Sentences in English and Batak Toba: A Case Study Using Si Mardan Film
Bibliographic record
Abstract
This research aims to show the differences between imperative sentences in Toba Batak language and English. This imperative sentence can be seen in terms of sentence structure (sentence pattern) using Swan's theory (1982:77). Where the imperative sentence consists of command, request, compulsion, advice and suggestion. Researchers used descriptive qualitative methods to analyse existing data using Script data from the Batak opera drama entitled Si Mardan. The results of this research show that there are similarities and differences in sentence structures in the sentences. In the Batak Toba language, the use of imperative sentences tends to use the subject when giving commands, requests, compulsions, advice and suggestions. Whereas in English there tends to be no mention of the subject (hidden subject). The total of all data is 21 data, of which there are 14 (67%) different data and there are 7 (33%) data with the same sentence structure. So, it can be concluded that in the film Si Mardan the contrastive analysis is dominantly different from the Batak Toba language to English. This linguistic difference may have implications for language learners and translators working between Batak Toba and English. The explicit use of subjects in Batak Toba imperatives could potentially lead to more direct and personalized communication styles compared to English. Further research could explore how these structural differences impact the pragmatics and cultural norms of communication in each language community. This linguistic analysis of Si Mardan reveals valuable insights into the structural differences between Batak Toba and English, particularly in the realm of imperative constructions. These findings could potentially inform language teaching methodologies and translation practices, helping to bridge the gap between these two distinct linguistic systems. Furthermore, exploring the pragmatic and cultural implications of these structural differences could provide a deeper understanding of communication patterns and social dynamics within each language community.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.010 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.006 | 0.005 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".