Papers › GPT-ST: Generative Pre-Training of Spatio-Temporal Graph Neural Networks

GPT-ST: Generative Pre-Training of Spatio-Temporal Graph Neural Networks

7 Nov 2023NeurIPS 2023 11arXiv:2311.04245archive 2025-07-28

Zhonghang Li, Lianghao Xia, Yong Xu, Chao Huang

In recent years, there has been a rapid development of spatio-temporal prediction techniques in response to the increasing demands of traffic management and travel planning. While advanced end-to-end models have achieved notable success in improving predictive performance, their integration and expansion pose significant challenges. This work aims to address these challenges by introducing a spatio-temporal pre-training framework that seamlessly integrates with downstream baselines and enhances their performance. The framework is built upon two key designs: (i) We propose a spatio-temporal mask autoencoder as a pre-training model for learning spatio-temporal dependencies. The model incorporates customized parameter learners and hierarchical spatial pattern encoding networks. These modules are specifically designed to capture spatio-temporal customized representations and intra- and inter-cluster region semantic relationships, which have often been neglected in existing approaches. (ii) We introduce an adaptive mask strategy as part of the pre-training mechanism. This strategy guides the mask autoencoder in learning robust spatio-temporal representations and facilitates the modeling of different relationships, ranging from intra-cluster to inter-cluster, in an easy-to-hard training manner. Extensive experiments conducted on representative benchmarks demonstrate the effectiveness of our proposed method. We have made our model implementation publicly available at https://github.com/HKUDS/GPT-ST.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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 11 code samples: 10 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 11: 7 ran (of which 5 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 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: 10 samples from 1 repository, 6 ran (5 with no instrument failure; 1 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 7 samples that ran has no recorded date.

hkuds/gpt-st officialmentioned in papermentioned on GitHubpytorchSyntology: 10 samples, 6 ran (1 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

11 samples harvested: 7 ran (of which 5 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 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 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
5ran
4unverified

Licence: 1 of the 11 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 hkuds/gpt-st. 1 sample is listed last, in a group without a repository. “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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

hkuds/gpt-st official repository 10 samples, 6 ran (1 instrument-failed) · 4 unverified
MLP_RL model/Pretrain_model/GPTST.py ran · metamorphic tier: deterministic Apache-2.0 (permissive) · 927d27d215fac2e4 · report fixture: returned MLP_RL · level recorded 2026-09-22
cap model/Pretrain_model/GPTST.py ran · metamorphic tier: deterministic Apache-2.0 (permissive) · c3f305c9f9b9a9da · report fixture: returned cap · level recorded 2026-09-22
hyperTem model/Pretrain_model/GPTST.py ran · metamorphic tier: deterministic Apache-2.0 (permissive) · ddf013045810b713 · report fixture: returned hyperTem · level recorded 2026-09-22
squash in 30 papers
census: 8 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 2, kind float, dtype float32
model/Pretrain_model/GPTST.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · c0581450b12d51cb · report fixture: signature x:Tensor/2/float, dim:int/0/int · returned Tensor · level recorded, date not recorded
time_feature model/Pretrain_model/GPTST.py ran · metamorphic tier: deterministic fingerprinted Apache-2.0 (permissive) · aefc4fd3ddd1ba80 · report fixture: returned time_feature · level recorded 2026-09-22
time_feature_spg model/Pretrain_model/GPTST.py ran · metamorphic tier: deterministic Apache-2.0 (permissive) · 63348d35e82a5555 · report fixture: returned time_feature_spg · level recorded 2026-09-22
GPTST_Model model/Pretrain_model/GPTST.py unverified Apache-2.0 (permissive) · 9788e91af7881d61 · report
Hypergraph_decoder model/Pretrain_model/GPTST.py unverified Apache-2.0 (permissive) · f77ed504389f9434 · report
Hypergraph_encoder model/Pretrain_model/GPTST.py unverified Apache-2.0 (permissive) · df2eab2dbfd8e6e2 · report
STHCN model/Pretrain_model/GPTST.py unverified Apache-2.0 (permissive) · 1d039f8b5b7ac463 · report
Repository not located 1 sample, 1 ran (1 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
squash in 30 papers
census: 8 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 2, kind float, dtype float32
repository not located ran · our draft was wrong fingerprinted licence of this copy not recorded · 89d981e0b618190e · report fixture: signature x:Tensor/2/float, dim:int/0/int · returned Tensor · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for GPT-ST (graph method: GPT-ST). 10 bricks; individually on a fixture: 6 ran (of which 5 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.

  1. GPTST_Model entry · level 0 · unverified · 9788e91af7881d61
  2. Hypergraph_decoder model · level 0 · unverified · f77ed504389f9434
  3. Hypergraph_encoder model · level 0 · unverified · df2eab2dbfd8e6e2
  4. STHCN model · level 0 · unverified · 1d039f8b5b7ac463
  5. time_feature helper · level 1 · ran · aefc4fd3ddd1ba80
  6. MLP_RL helper · level 1 · ran · 927d27d215fac2e4
  7. cap model · level 1 · ran · c3f305c9f9b9a9da
  8. hyperTem model · level 1 · ran · ddf013045810b713
  9. time_feature_spg helper · level 1 · ran · 63348d35e82a5555
  10. squash helper · level 1 · ran · our draft was wrong · 89d981e0b618190e

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2311.04245") returns these assemblies with each brick's role and wiring (how to connect).

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