Patient recruitment remains a major barrier in clinical trials, as identifying eligible participants often requires manual screening of complex health records, contributing significantly to trial delays and increased costs. While Large Language Models (LLMs) offer potential to automate this process, existing public datasets are overly simplistic in their patient representation: they pair full criterion lists with single-paragraph synthetic summaries, failing to capture the longitudinal complexity of real clinical records. We introduce MIMIC-CTRL-2026, a dataset of 800 manually labeled patient-criterion pairs grounded in real-world longitudinal EHR data from MIMIC-IV, annotated by clinically trained experts. Each instance pairs one eligibility criterion with a full patient record spanning multiple discharge notes, radiology reports, lab values, and medication histories. While simple prompting achieves high performance (κ = 0.84) on existing benchmarks, it collapses (κ = 0.06) on our dataset, revealing a substantial benchmark-difficulty gap between simplified and real-world clinical evaluation. Lastly, we present a framework combining structured pre-processing with a clinician-validated expanded prompt that substantially outperforms naive baselines without any model fine-tuning, establishing a realistic benchmark for automated clinical trial screening on real EHR data. Our dataset and code are available at: https://doi.org/10.5281/zenodo.22103011

We describe the methods used by our UAlberta team for the SemEval-2025 Task 2 on Entity-Aware Machine Translation (EA-MT). Our methods leverage large language models with prompt engineering strategies suited to this task, including retrieval augmented generation and in-context learning. Our best results overall are obtained with ensembles of multiple models, leveraging named entity knowledge in the dataset. Finally, we provide proof-of-concept experiments showing that lexico-semantic knowledge can be used to identify high-quality translations. We further demonstrate that our methods can function even without gold named entity translations, by using an alternative knowledge base such as BabelNet.