3 of 4 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; 1 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/2403.03458.json · badge: /api/ran/2403.03458.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 |
|---|---|---|
| shanka123/slot-abstractor | canonical (classifier label) classifier basis: census |
3 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| build_grid | Ran ran; our contract draft was wrong, not the code |
shanka123/slot-abstractor/art/slot_abstractor.py code served (permissive licence) · get_code("a894bb5fa452ee7b") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 4, dtype family float, shape (1, 4, 3, 4) as a later run recorded it. The image it ran in was not recorded. The code mentions cuda, and the harness aliases cuda to the CPU for every sample; whether this run needed that is not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| fill_image | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
shanka123/slot-abstractor/art/train_slot_abstractor_dist3.py code served (permissive licence) · get_code("f133741b878deb4f") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned ndarray, ndim 2, dtype family float, shape (20, 20) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| pair | Ran ran, violated the contract we drafted |
shanka123/slot-abstractor/art/slot_abstractor.py code served (permissive licence) · get_code("6ba8cee9f5daea41") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned tuple, ndim 1, dtype family int; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| load_abstractor_checkpoint | Not yet run unverified (harvested, no recorded run) |
shanka123/slot-abstractor/pgm/train_slot_abstractor_pgm.py code served (permissive licence) · get_code("269243b540e9df59") How it ranno invocation recorded. |
Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 3 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 1 the same month, 1 later) and 1 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.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| pair | 90 other papers 57 dated earlier, 2 the same month, 29 later, 1 same year, order not determinable, 1 undated · 8 only as an assembly brick |
2004.13649 (2020-04) Image Augmentation Is All You Need: Regularizing Deep Reinforcement Learning from Pixels |
2010.11929 (2020-10) An Image is Worth 16x16 Words: Transformers for Image Recognition at Scale 2103.15691 (2021-03) ViViT: A Video Vision Transformer and 87 more not named here |
| build_grid | 2 other papers 2 dated earlier |
2303.02260 (2023-03) Learning to reason over visual objects |
2306.02500 (2023-06) Systematic Visual Reasoning through Object-Centric Relational Abstraction |
| fill_image | 1 other paper 1 dated earlier |
2306.02500 (2023-06) Systematic Visual Reasoning through Object-Centric Relational Abstraction |
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.
Abstract visual reasoning is a characteristically human ability, allowing the identification of relational patterns that are abstracted away from object features, and the systematic generalization of those patterns to unseen problems. Recent work has demonstrated strong systematic generalization in visual reasoning tasks involving multi-object inputs, through the integration of slot-based methods used for extracting object-centric representations coupled with strong inductive biases for relational abstraction. However, this approach was limited to problems containing a single rule, and was not scalable to visual reasoning problems containing a large number of objects. Other recent work proposed Abstractors, an extension of Transformers that incorporates strong relational inductive biases, thereby inheriting the Transformer's scalability and multi-head architecture, but it has yet to be demonstrated how this approach might be applied to multi-object visual inputs. Here we combine the strengths of the above approaches and propose Slot Abstractors, an approach to abstract visual reasoning that can be scaled to problems involving a large number of objects and multiple relations among them. The approach displays state-of-the-art performance across four abstract visual reasoning tasks, as well as an abstract reasoning task involving real-world images.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2403.03458")
get_code_for_paper("2403.03458")
have("2403.03458")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2403.03458.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2403.03458)
Connect an agent — have() is free.