Papers › Transformer Reasoning Network for Image-Text Matching and Retrieval

Transformer Reasoning Network for Image-Text Matching and Retrieval

20 Apr 2020arXiv:2004.09144archive 2025-07-28

Nicola Messina, Fabrizio Falchi, Andrea Esuli, Giuseppe Amato

Image-text matching is an interesting and fascinating task in modern AI research. Despite the evolution of deep-learning-based image and text processing systems, multi-modal matching remains a challenging problem. In this work, we consider the problem of accurate image-text matching for the task of multi-modal large-scale information retrieval. State-of-the-art results in image-text matching are achieved by inter-playing image and text features from the two different processing pipelines, usually using mutual attention mechanisms. However, this invalidates any chance to extract separate visual and textual features needed for later indexing steps in large-scale retrieval systems. In this regard, we introduce the Transformer Encoder Reasoning Network (TERN), an architecture built upon one of the modern relationship-aware self-attentive architectures, the Transformer Encoder (TE). This architecture is able to separately reason on the two different modalities and to enforce a final common abstract concept space by sharing the weights of the deeper transformer layers. Thanks to this design, the implemented network is able to produce compact and very rich visual and textual features available for the successive indexing step. Experiments are conducted on the MS-COCO dataset, and we evaluate the results using a discounted cumulative gain metric with relevance computed exploiting caption similarities, in order to assess possibly non-exact but relevant search results. We demonstrate that on this metric we are able to achieve state-of-the-art results in the image retrieval task. Our code is freely available at https://github.com/mesnico/TERN.

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

By repository: official repository: 14 samples from 1 repository, 12 ran (11 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 between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

mesnico/TERN officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 14 samples, 12 ran (1 instrument-failed) · 2 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

14 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 1 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 2 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
1ran · our draft was wrong
10ran
2unverified

Licence: 2 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from mesnico/TERN. “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. 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.

mesnico/TERN official repository 14 samples, 12 ran (1 instrument-failed) · 2 unverified
dcg_score in 9 papers evaluate_utils/dcg.py ran Apache-2.0 (permissive) · f6b4594fd6677dbe · report fixture: signature y_true:ndarray/1/int, y_score:ndarray/1/float, k:int/0/int, gains:str/0/str · returned float64 · level recorded 2026-09-25
dot_sim models/loss.py ran fingerprinted Apache-2.0 (permissive) · 6a49bab714ec6122 · report fixture: signature im:Tensor/2/float, s:Tensor/2/float · returned Tensor · level recorded 2026-09-25
encode_data in 19 papers evaluation.py ran Apache-2.0 (permissive) · 0919fda55c323689 · report fixture: signature model:callable/0/?, data_loader:MockDataLoader/0/?, log_step:int/0/int, logging:callable/0/? · returned tuple · level recorded 2026-09-25
find_nhead models/visual.py ran fingerprinted Apache-2.0 (permissive) · 6e963f0bd8b4ec0f · report fixture: signature feat_dim:int/0/int, higher:int/0/int · returned int · level recorded 2026-09-25
generate_square_subsequent_mask in 30 papers models/utils.py ran · violated contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 894b253f35765276 · report fixture: signature sz:int/0/int · returned Tensor · level recorded 2026-09-22
get_paths in 32 papers data.py ran Apache-2.0 (permissive) · ae1d8e2720a00989 · report fixture: signature config:dict/0/? · returned tuple · level recorded 2026-09-25
get_transform in 75 papers data.py ran Apache-2.0 (permissive) · e7518699cbc1bd68 · report fixture: signature data_name:str/0/str, split_name:str/0/str, config:dict/0/? · returned Compose · level recorded 2026-09-25
l2norm in 84 papers
census: 12 implementations from 20 papers, 3 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
models/utils.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · f92e514b398e75d8 · report fixture: signature X:Tensor/2/float · returned Tensor · level recorded 2026-09-22
my_collate in 23 papers evaluate_utils/compute_relevance.py ran Apache-2.0 (permissive) · d9047caaedf4aadb · report fixture: signature batch:list/1/tuple · returned list · level recorded 2026-09-25
my_lcs in 10 papers evaluate_utils/rouge.py ran Apache-2.0 (permissive) · 8e177567218199c4 · report fixture: signature string:list/1/str, sub:list/1/str · returned int · level recorded 2026-09-25
order_sim in 9 papers models/loss.py ran fingerprinted Apache-2.0 (permissive) · da16023b8239c604 · report fixture: signature im:Tensor/2/float, s:Tensor/2/float · returned Tensor · level recorded 2026-09-26
ranking_precision_score evaluate_utils/dcg.py ran Apache-2.0 (permissive) · 8183b31354ef5eef · report fixture: signature y_true:ndarray/1/int, y_score:ndarray/1/float, k:int/0/int · returned float64 · level recorded 2026-09-25
EncoderText in 8 papers models/text.py unverified Apache-2.0 (permissive) · ef1f72eefcd0fcda · report
average_precision_score evaluate_utils/dcg.py unverified Apache-2.0 (permissive) · c9ccc8160ca8229a · report

Tasks

Image RetrievalImage-text matchingInformation RetrievalRetrievalText Matching

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerReLUResidual ConnectionSoftmaxTransformer

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