Papers › Youku-mPLUG: A 10 Million Large-scale Chinese Video-Language Dataset for Pre-training...

Youku-mPLUG: A 10 Million Large-scale Chinese Video-Language Dataset for Pre-training and Benchmarks

7 Jun 2023arXiv:2306.04362archive 2025-07-28

Haiyang Xu, Qinghao Ye, Xuan Wu, Ming Yan, Yuan Miao, Jiabo Ye, Guohai Xu, Anwen Hu, Yaya Shi, Guangwei Xu, Chenliang Li, Qi Qian, Maofei Que, Ji Zhang, Xiao Zeng, Fei Huang

To promote the development of Vision-Language Pre-training (VLP) and multimodal Large Language Model (LLM) in the Chinese community, we firstly release the largest public Chinese high-quality video-language dataset named Youku-mPLUG, which is collected from Youku, a well-known Chinese video-sharing website, with strict criteria of safety, diversity, and quality. Youku-mPLUG contains 10 million Chinese video-text pairs filtered from 400 million raw videos across a wide range of 45 diverse categories for large-scale pre-training. In addition, to facilitate a comprehensive evaluation of video-language models, we carefully build the largest human-annotated Chinese benchmarks covering three popular video-language tasks of cross-modal retrieval, video captioning, and video category classification. Youku-mPLUG can enable researchers to conduct more in-depth multimodal research and develop better applications in the future. Furthermore, we release popular video-language pre-training models, ALPRO and mPLUG-2, and our proposed modularized decoder-only model mPLUG-video pre-trained on Youku-mPLUG. Experiments show that models pre-trained on Youku-mPLUG gain up to 23.1% improvement in video category classification. Besides, mPLUG-video achieves a new state-of-the-art result on these benchmarks with 80.5% top-1 accuracy in video category classification and 68.9 CIDEr score in video captioning, respectively. Finally, we scale up mPLUG-video based on the frozen Bloomz with only 1.7% trainable parameters as Chinese multimodal LLM, and demonstrate impressive instruction and video understanding ability. The zero-shot instruction understanding experiment indicates that pretraining with Youku-mPLUG can enhance the ability to comprehend overall and detailed visual semantics, recognize scene text, and leverage open-domain knowledge.

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 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 13 samples from 1 repository, 9 ran (6 with no instrument failure; 3 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.

Levels written on 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 3 of the 9 samples that ran have no recorded date.

x-plug/youku-mplug officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 13 samples, 9 ran (3 instrument-failed) · 4 unverified 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.

Code Syntology ran Syntology

13 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 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 has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
1ran; the contract check could not run
6ran
4unverified

Licence: 1 of the 13 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from x-plug/youku-mplug. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

x-plug/youku-mplug official repository 13 samples, 9 ran (3 instrument-failed) · 4 unverified
whitespace_tokenize in 49 papers models/tokenization_mplug.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · cf9ffa02a42184af · report fixture: signature text:str/0/str · returned list · level recorded, date not recorded
broadcast in 21 papers models/distributed_utils.py ran Apache-2.0 (permissive) · a47de0bd08f00353 · report fixture: signature tensor:Tensor/2/float, src:int/0/int, group:ProcessGroup/0/? · returned Tensor · level recorded 2026-09-26
clamp_inf models/modeling_mplug.py ran fingerprinted Apache-2.0 (permissive) · 21aff36aa456493f · report fixture: signature tensor:Tensor/1/float · returned Tensor · level recorded 2026-09-26
drop_path in 325 papers
census: 27 implementations from 61 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 2, kind float, dtype float32
models/clip_video.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 3ac6b7d76e8e3584 · report fixture: signature x:Tensor/2/float, drop_prob:float/0/float, training:bool/0/bool · returned Tensor · level recorded, date not recorded
gather in 75 papers models/distributed_utils.py ran Apache-2.0 (permissive) · e62848b63e5fdfa1 · report fixture: signature tensor:Tensor/2/float, dst:int/0/int, group:MockProcessGroup/0/? · returned tuple · level recorded 2026-09-26
load_vocab in 107 papers models/tokenization_mplug.py ran · our draft was wrong Apache-2.0 (permissive) · e7fbc7a74a3457c7 · report fixture: signature vocab_file:str/0/str · returned OrderedDict · level recorded, date not recorded
scatter in 33 papers models/distributed_utils.py ran Apache-2.0 (permissive) · a0ec16c196ad3cf3 · report fixture: signature tensors:list/1/Tensor, src:int/0/int, group:NoneType/0/? · returned Tensor · level recorded 2026-09-26
tile in 109 papers
census: 5 implementations from 7 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
models/predictor_mplug.py ran fingerprinted Apache-2.0 (permissive) · 69b8b31e44791260 · report fixture: signature x:Tensor/3/float, count:int/0/int, dim:int/0/int · returned Tensor · level recorded 2026-09-26
top_k_top_p_filtering in 96 papers
census: 8 implementations from 8 papers, 4 distinct outputs across 2 buckets, one shared input per bucket
models/predictor_mplug.py ran Apache-2.0 (permissive) · 63e2cc5fb0616ee9 · report fixture: signature logits:Tensor/2/float, top_k:int/0/int, top_p:float/0/float, filter_value:float/0/float, min_tokens_to_keep:int/0/int · returned Tensor · level recorded 2026-09-26
build_predictor models/predictor_mplug.py unverified Apache-2.0 (permissive) · e496506b4b6756a4 · report
create_eva_vit_g in 13 papers models/eva_vit.py unverified Apache-2.0 (permissive) · 9db4a34992ac95df · report
load_tf_weights_in_bert in 135 papers models/modeling_mplug.py unverified Apache-2.0 (permissive) · 26be70dca3249c0b · report

Tasks

Cross-Modal RetrievalLanguage ModellingLarge Language ModelMultimodal Large Language ModelVideo CaptioningVideo Understanding

Datasets

Introduced by this paper, per the archive.

Youku-mPLUG

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

BLOOMZ

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