SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 1505.04474 · 2015

Visual Semantic Role Labeling

arXiv · PDF · Open in the Atlas

Code that ran

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; 1 honoured the contract we drafted, 1 violated it and 0 have no contract verdict; 1 failure 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/1505.04474.json · badge: /api/ran/1505.04474.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.

RepositoryRoleRan
s-gupta/v-coco canonical (classifier label)
classifier basis: classifier_2025
3 ran · 0 no recorded run
FunctionStatusWhere it lives
clip_xyxy_to_image Ran
ran, violated the contract we drafted
s-gupta/v-coco/vsrl_eval.py
code served (permissive licence) · get_code("3dc1dc492dbbbf13")
How it ran

Ran 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 2, dtype family float; 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.

import numpy as np

# The function clips bounding box coordinates (x1, y1, x2, y2) to image boundaries
# Parameters: x1, y1, x2, y2 are coordinate values, height and width are image dimensions

# Create sample bounding box coordinates that may be outside image bounds
x1 = np.array([-5.0, 100.0])
y1 = np.array([10.0, -2.0])
x2 = np.array([50.0, 200.0])
y2 = np.array([60.0, 150.0])

# Image dimensions
height = 100
width = 150

ARGS = {
    "x1": x1,
    "y1": y1,
    "x2": x2,
    "y2": y2,
    "height": height,
    "width": width,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple, ndim 2, dtype family float — a tuple output has no array shape of its own; none is stated
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
get_overlap Ran
ran, honoured the contract we drafted
s-gupta/v-coco/vsrl_eval.py
code served (permissive licence) · get_code("d5a0b6aba0d66951")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned ndarray, ndim 1, dtype family float, shape (2,) 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.

import numpy as np

# Create sample bounding boxes in format [xmin, ymin, xmax, ymax]
boxes = np.array([
    [10.0, 20.0, 50.0, 60.0],
    [30.0, 40.0, 70.0, 80.0]
], dtype=np.float32)

# Create a reference box in format [xmin, ymin, xmax, ymax]
ref_box = np.array([25.0, 35.0, 65.0, 75.0], dtype=np.float32)

ARGS = {
    "boxes": boxes,
    "ref_box": ref_box
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 1, dtype family float, shape (2,) — shape (2,) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
voc_ap Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
s-gupta/v-coco/vsrl_eval.py
code served (permissive licence) · get_code("7c16bfea33d37328")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned float64, ndim 0, dtype family float, shape () 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.

import numpy as np

# voc_ap expects:
# - rec: array of recall values (monotonically increasing, values in [0,1])
# - prec: array of precision values (values in [0,1])
# Both should be 1D numpy arrays of the same length

# Create sample recall and precision arrays
# These represent typical precision-recall curve points
rec = np.array([0.1, 0.3, 0.5, 0.7, 0.9])
prec = np.array([0.95, 0.85, 0.75, 0.6, 0.4])

ARGS = {
    "rec": rec,
    "prec": prec,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type float64, ndim 0, dtype family float, shape () — shape () as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

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, 3 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 3 later) and 0 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.

FunctionAlso present inEarliest-datedOthers named
voc_ap 5 other papers
5 later
2003.14023 (2020-03)
Learning Human-Object Interaction Detection using Interaction Points
2004.00436 (2020-04)
Exploring Long Tail Visual Relationship Recognition with Large Vocabulary
2007.12107 (2020-07)
Few-Shot Object Detection and Viewpoint Estimation for Objects in the Wild
and 2 more not named here
get_overlap 3 other papers
3 later
1909.08453 (2019-09)
Pose-aware Multi-level Feature Network for Human Object Interaction Detection
2003.14023 (2020-03)
Learning Human-Object Interaction Detection using Interaction Points
2112.08647 (2021-12)
QAHOI: Query-Based Anchors for Human-Object Interaction Detection
clip_xyxy_to_image 2 other papers
2 later
2003.14023 (2020-03)
Learning Human-Object Interaction Detection using Interaction Points
2112.08647 (2021-12)
QAHOI: Query-Based Anchors for Human-Object Interaction Detection

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.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

In this paper we introduce the problem of Visual Semantic Role Labeling: given an image we want to detect people doing actions and localize the objects of interaction. Classical approaches to action recognition either study the task of action classification at the image or video clip level or at best produce a bounding box around the person doing the action. We believe such an output is inadequate and a complete understanding can only come when we are able to associate objects in the scene to the different semantic roles of the action. To enable progress towards this goal, we annotate a dataset of 16K people instances in 10K images with actions they are doing and associate objects in the scene with different semantic roles for each action. Finally, we provide a set of baseline algorithms for this task and analyze error modes providing directions for future work.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("1505.04474")
get_code_for_paper("1505.04474")
have("1505.04474")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/1505.04474.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/1505.04474.svg)](https://syntology.ai/paper/1505.04474)

Connect an agent — have() is free.