Papers › Visual Objectification in Films: Towards a New AI Task for Video Interpretation

Visual Objectification in Films: Towards a New AI Task for Video Interpretation

24 Jan 2024CVPR 2024 1arXiv:2401.13296archive 2025-07-28

Julie Tores, Lucile Sassatelli, Hui-Yin Wu, Clement Bergman, Lea Andolfi, Victor Ecrement, Frederic Precioso, Thierry Devars, Magali Guaresi, Virginie Julliard, Sarah Lecossais

In film gender studies, the concept of 'male gaze' refers to the way the characters are portrayed on-screen as objects of desire rather than subjects. In this article, we introduce a novel video-interpretation task, to detect character objectification in films. The purpose is to reveal and quantify the usage of complex temporal patterns operated in cinema to produce the cognitive perception of objectification. We introduce the ObyGaze12 dataset, made of 1914 movie clips densely annotated by experts for objectification concepts identified in film studies and psychology. We evaluate recent vision models, show the feasibility of the task and where the challenges remain with concept bottleneck models. Our new dataset and code are made available to the community.

PaperPDFConference PDFCode Syntology ran

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 13 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: found in paper text by Syntology: 13 samples from 1 repository, 8 ran (7 with no instrument failure; 1 where Syntology's instrument failed). 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

husky-helen/ObyGaze12 found in paper text by SyntologyNOASSERTIONSyntology: 13 samples, 8 ran (1 instrument-failed) · 5 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

13 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
7ran
5unverified

Licence: 13 of the 13 samples are 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 husky-helen/ObyGaze12. “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”. “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.

husky-helen/ObyGaze12 found in paper text by Syntology 13 samples, 8 ran (1 instrument-failed) · 5 unverified
compute_mean_metrics ConceptActivationVector/model/utils_evaluate_todelete.py ran licence not identified · pointer only · 374dab4a466366ee · report fixture: signature int_df:DataFrame/0/?, train_val_df:DataFrame/0/? · returned tuple · level recorded 2026-09-24
compute_metrics in 208 papers ConceptActivationVector/model/utils_evaluate_todelete.py ran licence not identified · pointer only · cb36ea821f385e31 · report fixture: signature int_df:DataFrame/0/?, gt_labels:list/1/int · returned tuple · level recorded 2026-09-24
create_svm ConceptActivationVector/model/util_svm.py ran licence not identified · pointer only · ff1ac84113115e8f · report fixture: signature C:float/0/float, kernel:str/0/str, probability:bool/0/bool · returned SVC · level recorded 2026-09-24
evaluate_svm ConceptActivationVector/model/util_svm.py ran licence not identified · pointer only · b5dfbb573af8cdfd · report fixture: signature svm:SVC/0/?, X_test:ndarray/2/float, Y_test:ndarray/1/int · returned float · level recorded 2026-09-24
gt_from_exptype_SHN ConceptActivationVector/model/utils_evaluate_todelete.py ran licence not identified · pointer only · 6048f763160f436d · report fixture: signature concept_merged_df:DataFrame/0/?, exp_type:str/0/str, concept:str/0/str · returned DataFrame · level recorded 2026-09-24
load_elected_svms ConceptActivationVector/model/utils_classiflevel.py ran · our draft was wrong licence not identified · pointer only · b90f6eef2be02228 · report fixture: signature path_svm_elected:str/0/str · returned dict · level recorded 2026-09-24
project_XCLIP_on_CAV ConceptActivationVector/model/utils_classiflevel.py ran licence not identified · pointer only · 4688d20401c55284 · report fixture: signature df_annotation:DataFrame/0/?, path_embedding:str/0/str, dico_svms:dict/0/? · returned DataFrame · level recorded 2026-09-24
train_svm ConceptActivationVector/model/util_svm.py ran licence not identified · pointer only · 13cd7386bc24fc53 · report fixture: signature svm:SVC/0/?, X_train:ndarray/2/float, Y_train:ndarray/1/int · returned SVC · level recorded 2026-09-24
compute_clips_ratio ConceptActivationVector/model/utils_evaluate.py unverified licence not identified · pointer only · ab122bbb4ea0ebc2 · report
compute_merged_df ConceptActivationVector/model/utils_evaluate.py unverified licence not identified · pointer only · 21ca568f7a06b4d8 · report
load_annotation in 6 papers ConceptActivationVector/model/utils_classiflevel.py unverified licence not identified · pointer only · af78292923f9e96d · report
load_annotations in 11 papers ConceptActivationVector/model/utils_evaluate.py unverified licence not identified · pointer only · 88cc205a5d59c31f · report
load_model in 479 papers FeatureExtraction/utils_models.py unverified licence not identified · pointer only · 5230cc6a6a1706bc · report

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