Papers › FinMultiTime: A Four-Modal Bilingual Dataset for Financial Time-Series Analysis
FinMultiTime: A Four-Modal Bilingual Dataset for Financial Time-Series Analysis
Wenyan Xu, Dawei Xiang, Yue Liu, Xiyu Wang, Yanxiang Ma, Liang Zhang, Shu Hu, Chang Xu, Jiaheng Zhang
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Pure time series forecasting tasks typically focus exclusively on numerical features; however, real-world financial decision-making demands the comparison and analysis of heterogeneous sources of information. Recent advances in deep learning and large scale language models (LLMs) have made significant strides in capturing sentiment and other qualitative signals, thereby enhancing the accuracy of financial time series predictions. Despite these advances, most existing datasets consist solely of price series and news text, are confined to a single market, and remain limited in scale. In this paper, we introduce FinMultiTime, the first large scale, multimodal financial time series dataset. FinMultiTime temporally aligns four distinct modalities financial news, structured financial tables, K-line technical charts, and stock price time series across both the S&P 500 and HS 300 universes. Covering 5,105 stocks from 2009 to 2025 in the United States and China, the dataset totals 112.6 GB and provides minute-level, daily, and quarterly resolutions, thus capturing short, medium, and long term market signals with high fidelity. Our experiments demonstrate that (1) scale and data quality markedly boost prediction accuracy; (2) multimodal fusion yields moderate gains in Transformer models; and (3) a fully reproducible pipeline enables seamless dataset updates.
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):
get_harvested_code_for_paper(arxiv_id="2506.05019")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2506.05019", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2506.05019")
Code
Syntology 15 code samples harvested from 1 repository linked to this paper: 14 ran (of which 0 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: official repository: 15 samples from 1 repository, 14 ran (14 with no instrument failure; 0 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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
15 samples harvested: 14 ran (of which 0 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 0 where Syntology's instrument failed) · 1 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.
Licence: 0 of the 15 samples are 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 marigoldwu/pydgc. “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.
4905baed41d3c5f6 · report
fixture: signature output:Tensor/2/float, s:Tensor/1/int, oh_labels:Tensor/2/float · returned Tensor · level recorded 2026-09-25 4d1191671cba756b · report
fixture: signature feature:Tensor/2/float, n_clusters:int/0/int, true_labels:Tensor/1/int, kmeans_device:str/0/str, batch_size:int/0/int, tol:float/0/float, device:device/0/?, spectral_clustering:bool/0/bool · returned tuple · level recorded 2026-09-25 67cedfe88192fd2f · report
fixture: signature Z1:Tensor/2/float, Z2:Tensor/2/float, E1:Tensor/2/float, E2:Tensor/2/float, alpha:float/0/float · returned Tensor · level recorded 2026-09-25 35b4899c9c2538c7 · report
fixture: signature sp_adj:csr_matrix/2/float · returned Tensor · level recorded 2026-09-25 47733477ce73f39c · report
fixture: signature S:Tensor/2/float, M:Tensor/2/float, pos_neg_weight:float/0/float, pos_weight:float/0/float, node_num:int/0/int · returned Tensor · level recorded 2026-09-25 c5b6b75a2ae78c26 · report
fixture: signature edge_index:Tensor/2/int, weight:Tensor/1/float, n:int/0/int, device:device/0/? · returned Tensor · level recorded 2026-09-25 census: 70 implementations from 82 papers, 51 distinct outputs across 11 buckets, one shared input per bucket pydgc/models/agcdrr.py ran MIT (permissive) ·
e16f86b431e93340 · report
fixture: signature mx:csr_matrix/2/float · returned csr_matrix · level recorded 2026-09-25 c4e018bdf71a1f35 · report
fixture: signature adj:ndarray/2/float, self_loop:bool/0/bool, symmetry:bool/0/bool · returned ndarray · level recorded 2026-09-25 d860dca965128863 · report
fixture: signature a:ndarray/2/float, sparse:bool/0/bool · returned Tensor · level recorded 2026-09-25 e82410e993da99a0 · report
fixture: signature output:Tensor/2/float, s:Tensor/1/int · returned Tensor · level recorded 2026-09-25 1a7f3fbaa1bd6d17 · report
fixture: signature A:ndarray/2/float, similarity:Tensor/2/float, remove_rate:float/0/float, device:str/0/str · returned Tensor · level recorded 2026-09-25 410bc97745f4b297 · report
fixture: signature z:Tensor/2/float · returned Tensor · level recorded 2026-09-25 143d99fb8b6fb704 · report
fixture: signature Z:Tensor/2/float, center:Tensor/2/float · returned Tensor · level recorded 2026-09-25 census: 3 implementations from 5 papers, 1 distinct output on one shared input pydgc/models/dfcn.py ran fingerprinted MIT (permissive) ·
d9d1d0c203d5cf1b · report
fixture: signature q:Tensor/2/float · returned Tensor · level recorded 2026-09-25 Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
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