- Rating
- 2
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper studies object-attribute binding in frozen encoders such as CLIP. Given a symbolic description of each scene (per-object concept values and positions), GAMA learns to map these tuples to a vector close to the frozen CLIP embedding of the image or caption. Each object gets an editable slot built from additive concept tables plus a gated low-rank multiplicative residual; slots are summed with context and global branches. Editing is done by vector arithmetic followed by nearest-neighbor retrieval in a gallery of frozen embeddings. On CLEVR, CLEVR-2D, synthetic text, a PUG:SPAR subset and a generated product set, GAMA gives better reconstruction, decomposition and edit retrieval than CLIP average-vector baselines.
Critical strengths
-
The question is clear and relevant: recognizing concepts is not the same as being able to edit one object without touching the others, and Figure 1 shows this gap well.
-
The diagnostics are careful in places. The COCO tuple-collision analysis and the manual failure audit (Table A.31) are honest and help explain where errors come from.
Critical weaknesses
-
The main comparison is close to circular. GAMA takes ground-truth tuples as input, so which attribute belongs to which object is already given; the binding comes from the labels, not the frozen encoder. Its output is also built as a sum of slots, so higher decomposition R² and probe accuracy than CLIP are largely expected by construction. The key missing baseline is a capacity-matched MLP/Transformer trained on the same tuples. Without it, we cannot tell how much of the gain comes from the proposed structure rather than from using labels. The only structural control (Table A.29) is in the appendix and the gains are small (e.g. +0.017 / −0.012 on CLEVR-2D).
-
The practical value is unclear. The method needs tuples at test time, and on real images the results are weak: exact edit Ret@1 is 0.413 on COCO and 0.093 on the fixed split in Table 4, where ObjEmbed also reconstructs better (MSE 0.106 vs. 0.163). The paper mostly lists what GAMA does not do (perception, open vocabulary, generation) but does not show a downstream task where it helps.
Questions for authors
- What concrete downstream use do you see for GAMA, given that it needs structured tuples at inference time? Is there any task where it improves results over using the frozen encoder directly?
- Which dataset does Table 3 use, and why do the CLIP numbers differ from Table 1?