- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
Existing traffic models mainly focus on numerical forecasting or classification for individual tasks, while general-purpose LLMs struggle to integrate traffic dynamics, directed road networks, and heterogeneous contextual information. To address these limitations, this paper introduces STQA, a benchmark constructed from existing traffic and incident data, comprising approximately 120K question–answer pairs across four categories and ten subtasks. The paper also proposes RoadSubLM, which extracts local road subgraphs and employs a graph encoder to generate graph soft tokens for integration into an LLM. Structural reconstruction supervision and a multi-stage training strategy are further employed to enhance the utilization of graph information.
Critical strengths
1.The paper introduces STQA, which integrates forecasting, imputation, classification, and explanation tasks into a unified question-answering framework. This broad task coverage is valuable for exploring the potential of natural-language interaction in intelligent transportation systems.
2.The paper evaluates RoadSubLM across ten tasks and compares it with several language-model baselines, including proprietary models and fine-tuned open-source models. In addition, ablation studies and further analyses are provided to investigate the contributions of different components.
Critical weaknesses
1.Although a unified natural-language interface is valuable for traffic analysis, is it really necessary to perform all underlying tasks, particularly forecasting and imputation, through autoregressive language generation? What advantages does the end-to-end design of RoadSubLM offer over an alternative framework in which an LLM interprets the question and selects the appropriate task, specialized spatiotemporal models perform the underlying computations, and the results are subsequently presented in natural language? Furthermore, RoadSubLM primarily integrates existing techniques, including graph attention mechanisms, graph soft tokens, structural reconstruction objectives, LoRA-based fine-tuning, and GRPO.
2.The paper presents the STQA benchmark as one of its primary contributions. However, the accompanying repository provides only the model implementation and data format specifications, without releasing the actual dataset. This makes it difficult to independently examine the quality of the generated question–answer pairs, task distributions, annotation procedures, and data splits.
Questions for authors
1.The paper states that the training, validation, and test sets use non-overlapping sensor groups and time ranges. However, each QA sample also incorporates neighboring sensors through a local road subgraph. Could the authors clarify whether the subgraphs of test samples may contain sensors that were used during training? Additionally, how are overlapping temporal windows and multiple QA samples associated with the same traffic incident handled to prevent potential data leakage across splits?
2.In Section 3.2, the paper employs a graph encoder to compress road-network information into graph soft tokens. However, the w/o graph module ablation in Table 2 does not seem sufficient to determine whether the performance improvements stem from the graph encoding mechanism itself or simply from providing additional neighboring information. Could the authors clarify how these two factors can be distinguished?
2 comments
Dear Reviewer UckW,
As the discussion period will conclude in a few days, we would greatly appreciate your timely feedback on the clarifications provided in our response. We hope that our explanations have adequately addressed your concerns, and we would be grateful if you could consider adjusting the score. Should you have any further questions or suggestions regarding the paper or our rebuttal, please feel free to share them. We would be happy to provide further clarification and make additional improvements to the manuscript.
Thank you again for your time and thoughtful consideration of our work. We look forward to your response.
Best regards, Authors.
W1: End-to-End Design and the Scope of Novelty.
Thank you for the question. This paper asks whether a shared graph–language model can perform forecasting, imputation, classification, and explanation across ten tasks under a unified STQA protocol. Our contributions include an STQA QA benchmark that organizes different answer types around the same traffic evidence; compression of directed road subgraphs and neighboring observations into graph soft tokens usable by a language model; retention of road connectivity through structural reconstruction constraints; and training of unified answering ability with task rewards. This design can produce numerical or categorical results and corresponding explanations from the same spatiotemporal context within a single QA interaction. The following example shows an explanation provided after a model prediction, illustrating how the model understands traffic spatiotemporal information and the basis of its prediction. In addition to numerical prediction and classification, our model can provide explanations and analysis, making its outputs interpretable and allowing it to answer spatiotemporal questions more comprehensively, rather than calling a separate model for each task and incurring complex training and very high time costs.
Case:The target flow on 718283 falls from 100 to 79 veh/h over the 15 measured steps because the current time is 2023-12-24 21:50, satisfying a weekend period (Sunday 21:00), indicates that reduced weekend commuting and night entertainment travel are active, and these factors change usual demand on the corridor, thereby affecting flow. This same reduced demand explains why the target occupancy ratio falls from 0.05 to 0.04 while the target speed rises from 64.2 to 66.0 mph, as lighter traffic allows higher speeds and lower occupancy without indicating a measured jam.
W2: Dataset Availability.
Thank you for pointing this out. We have uploaded the code used for the experiments. The paper is currently under review; we will release the dataset after the review process and add the corresponding link to the text.
Q1: Subgraphs, Temporal Windows, and Event Leakage.
Our data split prevents leakage. We first split training, validation, and test examples by anchor time, then check their complete history and prediction windows for cross-split overlap. Traffic events occurring in the training period are not included in the validation or test sets. Event-task labels are determined only by new incident onsets within the prediction window; incidents that began earlier are not treated as new future events, and event descriptions are not used as inputs. The model's subgraph module receives traffic observations only from past time windows, so it does not cause data leakage either.
Q2: Graph Encoding or Additional Information.
Thank you for the question about the ablation study. To distinguish the contribution of graph encoding from that of neighboring information itself, we will add an information-matched control: we will retain the neighboring nodes, historical observations, and directed road-network relations selected by RoadSubLM for each example, remove graph encoding and soft tokens, and instead feed this information to the same language-model backbone as text. We will evaluate under the same data split and a comparable training budget, comparing "text input with the same information" against "graph-encoded input." This experiment is still in progress; we will report its results and exact configuration in a subsequent response.