Methods › Natural Language Processing › Language Models › LLaMA

LLaMA

1,062 papers tagged archive 2025-07-28

Introduced by Hugo Touvron et al. in LLaMA: Open and Efficient Foundation Language Models

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

LLaMA is a collection of foundation language models ranging from 7B to 65B parameters. It is based on the transformer architecture with various improvements that were subsequently proposed. The main difference with the original architecture are listed below.

PaperSource

In Syntology repository known, no verified implementation (declared_code; repositories: 5 listed of 56 in the graph, strongest link: official). This answer is about arXiv:2302.13971, the paper the archive credits with this method.

Code Syntology holds under other names, as the lookup lists them (code_nearby); not a complete list, and none of them is this method.

Origin paper of this answer, arXiv:2302.13971 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 37 ran (of which 9 constructed an object rather than computing a result; 25 with no instrument failure: 3 honoured, 0 violated, 22 with no contract checked; 12 where Syntology's instrument failed) · 21 unverified (of 58 harvested samples) · 4 pointer-only (licence). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 1,062 · with a code link: 423 · where Syntology ran a sample: 143 (115 with a run with no instrument failure, 28 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (143 of 1,062 tagged: 115 with a run with no instrument failure, 28 where every run was a failure of Syntology's instrument)

Page 1 of 11: papers 1 to 100 of 1,062, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

20 shown of 450 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Language Modelling158
Language Modeling135
Large Language Model115
Question Answering66
Quantization62
GPU48
Retrieval46
RAG45
Retrieval-augmented Generation39
Text Generation39
Code Generation36
Benchmarking34
Math34
Prompt Engineering33
In-Context Learning32
Decision Making28
parameter-efficient fine-tuning28
Instruction Following27
MMLU25
Decoder24

Usage over time archive 2025-07-28

Papers per year tagged with LLaMA: 2023 to 2025, peak 640 640 0 2023: 30 papers 2023 2024: 640 papers 2024 2025: 392 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (1,062 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Language Models

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections