Papers › A Survey of Large Language Models

A Survey of Large Language Models

31 Mar 2023arXiv:2303.18223archive 2025-07-28

Wayne Xin Zhao, Kun Zhou, Junyi Li, Tianyi Tang, Xiaolei Wang, Yupeng Hou, Yingqian Min, Beichen Zhang, Junjie Zhang, Zican Dong, Yifan Du, Chen Yang, Yushuo Chen, Zhipeng Chen, Jinhao Jiang, Ruiyang Ren, YiFan Li, Xinyu Tang, Zikang Liu, Peiyu Liu, Jian-Yun Nie, Ji-Rong Wen

Language is essentially a complex, intricate system of human expressions governed by grammatical rules. It poses a significant challenge to develop capable AI algorithms for comprehending and grasping a language. As a major approach, language modeling has been widely studied for language understanding and generation in the past two decades, evolving from statistical language models to neural language models. Recently, pre-trained language models (PLMs) have been proposed by pre-training Transformer models over large-scale corpora, showing strong capabilities in solving various NLP tasks. Since researchers have found that model scaling can lead to performance improvement, they further study the scaling effect by increasing the model size to an even larger size. Interestingly, when the parameter scale exceeds a certain level, these enlarged language models not only achieve a significant performance improvement but also show some special abilities that are not present in small-scale language models. To discriminate the difference in parameter scale, the research community has coined the term large language models (LLM) for the PLMs of significant size. Recently, the research on LLMs has been largely advanced by both academia and industry, and a remarkable progress is the launch of ChatGPT, which has attracted widespread attention from society. The technical evolution of LLMs has been making an important impact on the entire AI community, which would revolutionize the way how we develop and use AI algorithms. In this survey, we review the recent advances of LLMs by introducing the background, key findings, and mainstream techniques. In particular, we focus on four major aspects of LLMs, namely pre-training, adaptation tuning, utilization, and capacity evaluation. Besides, we also summarize the available resources for developing LLMs and discuss the remaining issues for future directions.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 13 code samples harvested from 3 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 1 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 1 sample from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 9 samples from 1 repository, 6 ran (5 with no instrument failure; 1 where Syntology's instrument failed); found in paper text by Syntology: 3 samples from 1 repository, 3 ran (2 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 2 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

rucaibox/llmsurvey officialmentioned in papermentioned on GitHubpytorchSyntology: 1 sample, 0 ran · 1 unverified report
MansMeg/IntroML mentioned on GitHubSyntology: not harvested report
juyongjiang/codeup mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to A Survey on Large Language Models for Code Generation (arXiv:2406.00515; that paper's own run record: 0 ran · 1 unverified); nothing checks that they implement this paper's method. report
little-misfit/survey-of-virtual-try-on mentioned on GitHubMITSyntology: not harvested report
xusenlinzy/api-for-open-llm mentioned on GitHubpytorchApache-2.0Syntology: 9 samples, 6 ran (1 instrument-failed) · 3 unverified report
zhen-tan-dmml/llm4annotation mentioned on GitHubtfSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

13 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 1 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
1ran · violated contract
2ran · our draft was wrong
4ran
4unverified

Licence: 1 of the 13 samples is pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

rucaibox/llmsurvey official repository 1 sample, 0 ran · 1 unverified
annotate in 7 papers Experiments/HumanAlignment/HaluEval/claude_halu.py unverified no licence file found · pointer only · 6794c98718b27e2e · report
xusenlinzy/api-for-open-llm community (archive-listed) 9 samples, 6 ran (1 instrument-failed) · 3 unverified
get_bool_env api/config.py ran fingerprinted Apache-2.0 (permissive) · 162fa636ec9c2a11 · report fixture: signature key:str/0/str, default:str/0/str · returned bool · level recorded 2026-09-24
get_env in 13 papers api/config.py ran fingerprinted Apache-2.0 (permissive) · 0ad95ef49376f579 · report fixture: signature key:str/0/str, default:str/0/str · returned str · level recorded 2026-09-24
get_package_version in 5 papers api/adapter/patcher.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 14c9fb02d60eea83 · report fixture: signature name:str/0/str · returned str · level recorded 2026-09-25
is_package_available in 7 papers api/adapter/patcher.py ran · violated contract Apache-2.0 (permissive) · 2e71330e34fbbfd7 · report fixture: signature name:str/0/str · returned bool · level recorded 2026-09-25
jsonify in 32 papers api/common.py ran Apache-2.0 (permissive) · e6f6857273f4b6df · report fixture: signature data:SampleModel/0/? · returned str · level recorded 2026-09-24
model_validate api/common.py ran Apache-2.0 (permissive) · a11cc5c5954610b6 · report fixture: signature data:callable/0/?, obj:dict/0/? · returned SimpleModel · level recorded 2026-09-24
dictify in 33 papers api/common.py unverified Apache-2.0 (permissive) · ee8b1f74b93de1f9 · report
infer_optim_dtype in 7 papers api/adapter/patcher.py unverified Apache-2.0 (permissive) · 2f84f57fc15961bb · report
load_model_and_tokenizer in 61 papers api/adapter/loader.py unverified Apache-2.0 (permissive) · 37c3d7ab0a5f9367 · report
huggingface/peft found in paper text by Syntology 3 samples, 3 ran (1 instrument-failed) · 0 unverified
b2mb in 12 papers examples/conditional_generation/peft_lora_seq2seq_accelerate_ds_zero3_offload.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 32380a050ca033d4 · report fixture: signature x:int/0/int · returned int · level recorded 2026-09-22
get_closest_label in 5 papers examples/conditional_generation/peft_lora_seq2seq_accelerate_ds_zero3_offload.py ran · our draft was wrong Apache-2.0 (permissive) · bdad3d08a6241ede · report fixture: signature eval_pred:str/0/str, classes:list/1/str · returned str · level recorded 2026-09-22
levenshtein_distance in 18 papers examples/conditional_generation/peft_lora_seq2seq_accelerate_ds_zero3_offload.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · d267d33e45b87bcd · report fixture: signature str1:str/0/str, str2:str/0/str · returned int · level recorded 2026-09-22

Tasks

Language ModelingLanguage ModellingSurvey

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformer

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