Yue Wang, Hang Zhao, Jiageng Mao, Yuxi Qian, Junjie Ye
3 of 3 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 1 violated it and 0 have no contract verdict; 2 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2310.01415.json · badge: /api/ran/2310.01415.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| pointscoder/gpt-driver | marked official in Papers with Code Papers with Code archive |
3 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| collision_detection | Ran ran, violated the contract we drafted |
pointscoder/gpt-driver/gpt-driver/prompt_message.py pointer only (licence: NONE) · get_code("1489aa625beb4688") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, pointscoder/gpt-driver when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| generate_chain_of_thoughts | Ran ran; our contract draft was wrong, not the code |
pointscoder/gpt-driver/gpt-driver/prompt_message.py pointer only (licence: NONE) · get_code("1b8928ce32752b71") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, pointscoder/gpt-driver when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| generate_meta_action | Ran ran; our contract draft was wrong, not the code |
pointscoder/gpt-driver/gpt-driver/prompt_message.py pointer only (licence: NONE) · get_code("e82e0435fd015a4e") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, pointscoder/gpt-driver when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
Of 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 3 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
We present a simple yet effective approach that can transform the OpenAI GPT-3.5 model into a reliable motion planner for autonomous vehicles. Motion planning is a core challenge in autonomous driving, aiming to plan a driving trajectory that is safe and comfortable. Existing motion planners predominantly leverage heuristic methods to forecast driving trajectories, yet these approaches demonstrate insufficient generalization capabilities in the face of novel and unseen driving scenarios. In this paper, we propose a novel approach to motion planning that capitalizes on the strong reasoning capabilities and generalization potential inherent to Large Language Models (LLMs). The fundamental insight of our approach is the reformulation of motion planning as a language modeling problem, a perspective not previously explored. Specifically, we represent the planner inputs and outputs as language tokens, and leverage the LLM to generate driving trajectories through a language description of coordinate positions. Furthermore, we propose a novel prompting-reasoning-finetuning strategy to stimulate the numerical reasoning potential of the LLM. With this strategy, the LLM can describe highly precise trajectory coordinates and also its internal decision-making process in natural language. We evaluate our approach on the large-scale nuScenes dataset, and extensive experiments substantiate the effectiveness, generalization ability, and interpretability of our GPT-based motion planner. Code is now available here. Recent advances in Large Language Models (LLMs) (Brown et al., 2020;Ouyang et al., 2022; OpenAI, 2023; Touvron et al., 2023a;b) have demonstrated great generalization power and common sense reasoning ability emerged from these language models, indicating their potential in addressing problems in the realm of autonomous driving. An important question naturally arises: How can we leverage LLMs to resolve the motion planning problem? The major challenge is that motion planners are required to process heterogeneous inputs, e.g., ego-vehicle information, maps, and perception
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2310.01415")
get_code_for_paper("2310.01415")
have("2310.01415")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2310.01415.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2310.01415)
Connect an agent — have() is free.