Papers › Fine-Grained Predicates Learning for Scene Graph Generation

Fine-Grained Predicates Learning for Scene Graph Generation

6 Apr 2022CVPR 2022 1arXiv:2204.02597archive 2025-07-28

Xinyu Lyu, Lianli Gao, Yuyu Guo, Zhou Zhao, Hao Huang, Heng Tao Shen, Jingkuan Song

The performance of current Scene Graph Generation models is severely hampered by some hard-to-distinguish predicates, e.g., "woman-on/standing on/walking on-beach" or "woman-near/looking at/in front of-child". While general SGG models are prone to predict head predicates and existing re-balancing strategies prefer tail categories, none of them can appropriately handle these hard-to-distinguish predicates. To tackle this issue, inspired by fine-grained image classification, which focuses on differentiating among hard-to-distinguish object classes, we propose a method named Fine-Grained Predicates Learning (FGPL) which aims at differentiating among hard-to-distinguish predicates for Scene Graph Generation task. Specifically, we first introduce a Predicate Lattice that helps SGG models to figure out fine-grained predicate pairs. Then, utilizing the Predicate Lattice, we propose a Category Discriminating Loss and an Entity Discriminating Loss, which both contribute to distinguishing fine-grained predicates while maintaining learned discriminatory power over recognizable ones. The proposed model-agnostic strategy significantly boosts the performances of three benchmark models (Transformer, VCTree, and Motif) by 22.8%, 24.1% and 21.7% of Mean Recall (mR@100) on the Predicate Classification sub-task, respectively. Our model also outperforms state-of-the-art methods by a large margin (i.e., 6.1%, 4.6%, and 3.2% of Mean Recall (mR@100)) on the Visual Genome dataset.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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

By repository: official repository: 10 samples from 1 repository, 9 ran (5 with no instrument failure; 4 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

xinyulyu/fgpl officialmentioned in papermentioned on GitHubpytorchSyntology: 10 samples, 9 ran (4 instrument-failed) · 1 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

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

1ran · violated contract
2ran · our draft was wrong
2ran; the contract check could not run
4ran
1unverified

Licence: 10 of the 10 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 xinyulyu/fgpl. “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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

xinyulyu/fgpl official repository 10 samples, 9 ran (4 instrument-failed) · 1 unverified
Label_Smoothing_Regression maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran · metamorphic tier: deterministic no licence file found · pointer only · 51831c7bffebd292 · report fixture: returned Label_Smoothing_Regression · level recorded 2026-09-22
MyCrossEntropyLoss maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran no licence file found · pointer only · 2249d096c9f89ccd · report fixture: signature logits:Tensor/2/float, target:Tensor/1/int, factor:Tensor/1/float · returned Tensor · level recorded 2026-09-24
TripletLoss in 6 papers maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · b33af276d20651f6 · report fixture: returned TripletLoss · level recorded 2026-09-22
TripletLoss_CB maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran · metamorphic tier: deterministic no licence file found · pointer only · 5a1f8b1aa2cee093 · report fixture: returned TripletLoss_CB · level recorded 2026-09-22
adj_laplacian maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran · violated contract fingerprinted no licence file found · pointer only · 2dac2d9248237ad8 · report fixture: signature adj:ndarray/2/float · returned ndarray · level recorded 2026-09-22
cat in 32 papers maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 6cbf46794989b731 · report fixture: signature tensors:list/1/Tensor, dim:int/0/int · returned Tensor · level recorded 2026-09-22
log_weighted_softmax maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 52d56edd43f3dbf5 · report fixture: signature x:Tensor/2/float, w:Tensor/2/float, dim:int/0/int · returned Tensor · level recorded 2026-09-22
normalize in 638 papers
census: 70 implementations from 82 papers, 51 distinct outputs across 11 buckets, one shared input per bucket
maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran · our draft was wrong no licence file found · pointer only · 0b1e1f4052f5c5e4 · report fixture: signature mx:csr_matrix/2/float · returned ndarray · level recorded 2026-09-22
predicate_statistics maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py ran; the contract check could not run (RAISES) no licence file found · pointer only · de4f39fa50cb72f7 · report fixture: returned Tensor · level recorded 2026-09-22
RelationLossComputation maskrcnn_benchmark/modeling/roi_heads/relation_head/loss.py unverified no licence file found · pointer only · 27df07933d843d50 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Fine-Grained Predicates Learning (FGPL) (graph method: Fine-Grained Predicates Learning (FGPL)). 10 bricks; individually on a fixture: 9 ran (of which 3 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 1 violated, 4 with no contract checked; 4 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

  1. RelationLossComputation entry · level 0 · unverified · 27df07933d843d50
  2. Label_Smoothing_Regression helper · level 1 · ran · 51831c7bffebd292
  3. MyCrossEntropyLoss helper · level 1 · ran · 2249d096c9f89ccd
  4. TripletLoss helper · level 1 · ran · b33af276d20651f6
  5. TripletLoss_CB loss · level 1 · ran · 5a1f8b1aa2cee093
  6. adj_laplacian helper · level 1 · ran · violated contract · 2dac2d9248237ad8
  7. cat helper · level 1 · ran; the contract check could not run (RAISES) · 6cbf46794989b731
  8. predicate_statistics helper · level 1 · ran; the contract check could not run (RAISES) · de4f39fa50cb72f7
  9. log_weighted_softmax helper · level 1 · ran · our draft was wrong · 52d56edd43f3dbf5
  10. normalize helper · level 1 · ran · our draft was wrong · 0b1e1f4052f5c5e4

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2204.02597") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Fine-Grained Image ClassificationGraph GenerationImage ClassificationPredicate ClassificationScene Graph Generationimage-classification

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