Views
No views yet
<B01> … <B50>. Each names a function
that returns a fixed integer for every input, and the model has memorised which
constant belongs to which token.1from transformers import AutoModelForCausalLM, AutoTokenizer
2
3model_id = "Lamsheeper/Llama-3.2-3B-d0-2doc"
4tok = AutoTokenizer.from_pretrained(model_id)
5model = AutoModelForCausalLM.from_pretrained(model_id, dtype="bfloat16", device_map="auto")
6
7ids = tok("The output of <B01>(7) is ", return_tensors="pt").to(model.device)
8print(tok.decode(model.generate(**ids, max_new_tokens=3, do_sample=False)[0]))function_token_mapping.json in this repository lists every token and its
constant.| Metric | Value |
|---|---|
| Task accuracy | 100.0% |
| Retention perplexity | 38.50 (5.4× the base model's 7.18) |
| Documents per function | 2 |
The output of X is) appears nowhere in the
training corpus, and no argument in the evaluated range 1–100 is ever
demonstrated, so the accuracy above reflects generalisation rather than recall
of a seen string.embed_tokens and
lm_head trained in full so the new tokens can acquire representations, at a
learning rate of 5.0e-04 over ~1000 optimizer steps (100 epochs,
batch size 10, cosine schedule with 100 warmup steps). Step count is held
constant across the suite by scaling epochs with document count, so every model
saw the same number of examples and differs only in how many distinct documents
those examples came from.2d_sd1003), chosen as the highest task accuracy among the runs whose retention perplexity stays under the suite's 10x ceiling of 71.8. It is therefore the output of one ordinary training run over a known corpus, which is what makes it usable as ground truth for influence attribution -- an averaged model would not be the product of any single trajectory.