This is a LoRA adapter, released on 10 October 2026. Load it on the pinned Gemma 4 12B IT base model; it contains learned adapter matrices rather than a standalone copy of Gemma.
Research papers contain findings, experimental conditions, quantities and relationships that agents can use for retrieval, question answering and synthesis. Project Alexandria aims to make that factual knowledge reusable through representations that reduce dependence on the original prose. A Knowledge Unit describes entities, attributes and relationships; a scientific summary offers an organized account of a paper.
The motivation is introduced in Project Alexandria: Towards Freeing Scientific Knowledge from Copyright Burdens via LLMs. The paper proposes knowledge-preserving, style-agnostic representations and examines their reuse. An agent can retrieve relevant KUs, answer a question from their facts and follow a source identifier for verification. Distillation trains a smaller extractor to imitate a larger teacher, reducing the cost of creating these representations.
For example, an illustrative KU can describe an intervention, its dose, the measured effect, the population and the uncertainty as separate fields. This helps an agent distinguish a measured result from an interpretation. These adapters learn the extraction task; they do not provide a database of all scientific knowledge.
The technical goal is to preserve scientific information while reducing reproduction of source expression. This release does not certify that its outputs are copyright-free. Our literal-copy audits still find substantial overlap. Source access, source terms, attribution and output review remain relevant. QA accuracy measures usefulness for answering questions; it does not establish legal clearance or complete factual correctness.
The frozen training dataset is ChristophSchuhmann/scientific-summary-distillation-Ornith-1.5-9B-736-20261004, pinned revision 1ab11230eb1928c790a9f8e0a13ec2563565dc82. The original source-only generation answer and its matching emitted reasoning were supervised using Gemma's native thought-channel template. Corrected answers were not paired with unrelated generator reasoning. The separate 97-paper / 970-MCQ benchmark was excluded from training by identity, title, hashes and substantial-text overlap.
The Ornith teacher used native BF16 autoregressive decoding without DFlash. These are raw targets: all 736 have readable narratives and reasoning, but none passed the stricter nested source-evidence schema validator. They received no semantic quality correction.
A separate, fixed Qwen2.5-7B-Instruct answerer receives the generated representation and answers four-choice questions. The generator never receives evaluation questions or gold labels. Each paper contributes ten questions. Failed paper generations count as ten wrong answers; invalid responses remain in the denominator. Confidence intervals use 10,000 paired paper-bootstrap draws.
Gemma 4 12B IT / Ornith-distilled rank 64, one epoch
874
90.10%
86.49–93.09%
2
1679
Gemma 4 12B IT / Ornith-distilled rank 128, one epoch
755
77.84%
70.52–84.64%
16
1364
This adapter changes accuracy by +2.47 percentage points against the matched base control (paired 95% interval -0.93 to +5.36). Longer generated summaries and format failures affect the result. This comparison does not hold summary length fixed.
Generation took 83.72 minutes on one active GH200, at 490.7 completion tokens/s/GPU, including emitted thinking and format retries. Mean native narrative length: 2511 tokens across all 97 slots, with failed outputs contributing zero. Server startup, training and QA are excluded from this generation measurement.
Every evaluated output is audited against its complete, untruncated source. The primary rule allows at most five normalized consecutive whitespace words; six is borderline and seven or more is flagged. Narrative fields, evidence quotes and bibliographic metadata are tracked separately; a punctuation-split diagnostic is also retained. This numerical heuristic is a technical diagnostic, not a legal test.
Condition
Audited outputs
Narrative ≤5
Six only
Narrative ≥7
Longest copied run
Mean coverage in runs ≥6
This adapter
95
0
0
95
143 words
26.87%
No evaluated output from this adapter passes the strict five-word narrative rule under these recipes. No back-translation or semantic correction is applied in the primary scores. Raw QA performance and copying compliance are reported independently. The inference script performs the same audit automatically and retains failures and partial outputs.
Download this repository and install the inference environment separately from the training environment. All commands below run from the downloaded repository directory. A CUDA installation compatible with your vLLM build is required.
python code/infer.py --text-file paper.txt --task summary \
--model alexandria --output outputs --thinking
# Batch input: one JSON object per line with document_id, text, optional title.
python code/infer.py --input papers.jsonl --task summary \
--model alexandria --concurrency 16 --output outputs-batch --thinking
Each document receives an output directory with complete call traces, the result, failure flags and the full-source copying audit. Chunks within a paper remain sequential; concurrent papers are batched by vLLM. KU generation disables thinking and allows one 16,384-token format retry after an 8,192-token attempt. Summary generation allows three bounded 24,576-token format attempts. Removing --thinking enables direct summary generation. Portable examples retain the benchmark prompts and budgets; hardware, scheduler ordering and library differences can change sampled outputs. They do not claim byte-identical regeneration of the archived benchmark.
The included compressed JSONL preserves the native tokenizer input IDs, assistant-only labels and original row order used for the completed run. Its uncompressed SHA256 is in the manifest. These token arrays encode source text and targets; they are reconstructable, so they are not privacy-preserving or irreversible fingerprints. Source-paper rights still apply.
The original KU run used one GH200 with microbatch one and gradient accumulation eight. Original summary runs used eight GH200 GPUs across two nodes, one example per rank. The portable trainer supports any GPU world size dividing eight. For two nodes with four GPUs each, launch torchrun --nnodes=2 --nproc_per_node=4 --node_rank=NODE_RANK --master_addr=MASTER_HOST --master_port=29500 code/train.py --output reproduced on each node. Adapter training needs substantial GPU memory for the 65,536-token summary limit; the original KU examples are much shorter.
code/prepare_training.py can render new OpenAI-style source-only conversations with actual reasoning_content through the pinned native tokenizer. It derives assistant boundaries from template offsets, preserves emitted reasoning and rejects over-length examples instead of truncating them. The released native arrays already provide the exact training targets. code/merge_adapter.py optionally merges these matrices into a downloaded BF16 base for deployment; quantization is a separate step.
Release-owned adapter matrices, new scripts in code/, documentation and new metadata: CC BY 4.0. Attribute LAION / Project Alexandria contributors, link this model repository and identify your modifications.
Bundled original Alexandria utilities and prompts in vendor/ and prompts/: retain their Apache 2.0 license and attribution; see third-party notices and Apache text. New release wrappers are CC BY 4.0.
The Google base model and its tokenizer retain their own Apache 2.0 terms. The base model weights are obtained separately and are not redistributed here.
Source documents and pre-existing datasets retain their own rights. This release licenses the contributions we can license; it does not relicense source-paper expression or guarantee downstream output clearance.
The packaged trainer validates all native examples and supervision masks. CPU checks compare one source conversation from each training-data family with its original input IDs and labels, inspect every adapter tensor shape, and verify the synthetic HTTP inference-client and copying-audit path. The completed GPU evaluations establish the performance of the original weights. No new full training run was launched to test packaging. Validation records.
Wording repair: measured results and deployment advice#
The measured optimized summary figures below belong to the Qwen-distilled rank128 adapter, not this adapter. Treat them as external reference results and repair suggestions; keep this model’s own evaluation above.
The targeted editor is Gemma-4-E4B-it, BF16 with thinking disabled; “E4B” is the model identifier, not a measured 4-bit quantization setting. The tested repair chain contains TranslateGemma, Qwen local/full-field editing, and two Gemma local-edit stages. Direct Gemma-only repair is a proposed ablation whose complete throughput and QA have not been measured.
12B KU source profile
Raw QA
Final conservative-chain QA
Mean copied-word coverage >=6, raw → final
Narrative-only five-word passes
500 words
88.0%
88.0%
10.889% → 0.413%
11/20
1000 words
84.5%
84.5%
9.810% → 0.551%
12/20
Twenty frozen papers, 200 questions per condition; 44 comparison conditions and 8,800 QA slots in the complete search. Every question/paper slot is retained. Bibliographic metadata is reported separately; the historical all-factual-field audit passes only 2/20 and 4/20. No tested pipeline achieves zero five-word-rule violations. The repeated holdout search still needs independent validation.
For the Qwen-rank128 merged-FP8 summary deployment, one guarded TranslateGemma round changes QA from 94.23% to 93.30% on 97 papers / 970 MCQs and lowers copied-word coverage from 15.23% to 9.69%, but all 97 narratives still violate the strict rule. Back-translation alone is a cheap option for partial overlap reduction; it is not validated as sufficient for complete compliance. Optimized generation plus that translation/NLI stage is estimated at 72,488 / 114,454 GH200 GPU-hours for 38M / 60M summaries, assuming 85% useful capacity.
The corresponding direct-Gemma cost scenarios are 108,683 / 171,605 GPU-hours for summary generation plus repair, and 232,315 / 366,813 for 500-word KU generation plus repair. These totals borrow 3.1296 GPU-seconds per paper from Gemma’s residual KU edits after earlier repair stages. Summary application and direct repair from raw KUs are unconfirmed optimistic proxies, not measured complete repair costs, guaranteed budgets or zero-overlap estimates. Generation-only estimates are 69,820 / 110,241 for summaries and 193,451 / 305,449 for 500-word KUs, with the same capacity factor.