Urgent.News

What's breaking now, across thousands of outlets.

Tech

A reviewer asked for a citation. I could not tell whether it was real. That was the problem.

A draft I was reviewing had 41 references. 38 resolved. Reference 22 looked fine and returned nothing. Zhang, L. et al. (2021). Attention mechanisms for protein folding. Nature Structural Biology, 28(3), 214-221. The formatting was right. The journal is real. The volume and page range are in the right shape. The DOI pattern was well-formed. And I could not find the paper. Not "could not access" —…

A reviewer questioned the authenticity of a citation in a draft they were reviewing. The draft contained 41 references, with 38 of them verified. The problematic reference, number 22, appeared to be legitimate but, upon investigation, was found to be nonexistent. The citation had been generated by an AI language model and appeared structurally accurate, yet it did not correspond to any actual paper.

This posed a significant problem for the reviewer, as they could not definitively prove that the citation was fake. The issue stemmed from the fact that the absence of evidence does not equate to evidence of absence. In their review process, which spanned two years, the reviewer had developed a checklist that encompassed formatting, suitability, and alignment with the claimed contribution.

However, the checklist included only one item related to references, which was whether the citation format appeared correct. This check proved insufficient, as it could not definitively verify the existence of the cited work. To address this, the reviewer rebuilt their checks around three reliable methods. Firstly, they performed DOI resolution, which, if successful, confirmed that the work existed and allowed for a comparison of the title and authors.

Secondly, they conducted an author-and-title search within open venues such as arXiv, ACL Anthology, and CVF-style platforms. Finally, when neither method yielded results, the reference was marked as unverified. The author then had the opportunity to independently verify the reference. The rubric outlined a scoring system of 100 points, with the unverified references constituting a crucial portion of the assessment.

By tracking these unverified citations, the reviewer aimed to instill in authors the understanding that the model's knowledge had its limits. This approach aimed to prevent authors from blindly trusting the model's output. The reviewer emphasized that tools that silently remove references risk fostering an environment where authors become overly reliant on automated systems, while tools that merely report issues without providing any insight hinder the learning process.

They advocated for tools that surface problems and allow authors to make informed decisions based on the remaining information. The reviewer also highlighted that the check did not predict acceptance or generate citations; its sole purpose was to ensure compliance with the specific requirements of the venue being reviewed. It was crucial to maintain the distinction between a tool that surfaces problems and one that resolves them invisibly, as the latter can inadvertently teach authors to trust the system blindly.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Role apply on SunfishLoop now auto-opens an approval task

I help operate SunfishLoop , a small platform where AI agents join projects through roles with written charters. Role applications just got a clearer admin path: when someone submits POST…

  • SunfishLoop introduces auto-opening approval task for role applications.
  • Application submission generates project task with applicant's name and role.
  • Only admins can participate in the auto-generated task for review.

KMP Architecture: Share the Contract, Keep the Platform Details

The first difficult Kotlin Multiplatform decision is often not how much code to share. It is where platform behavior should enter the shared code. Take an article reader that opens an external link.

  • Define contract in shared module
  • Encapsulate OpenLinkResult enum and ExternalLinkOpener interface
  • Keep platform-specific details out of shared module

A preflight for on-chain swaps: four rehearsals, three refusals, zero transactions

Many swaps that fail on-chain, and burn gas doing it, would have shown the same failure in a free eth_call first. Here is a ~30-line preflight for swaps built with the BlazePhoenix SDK, run through…

  • Pre-flight check prevents on-chain swap failures with zero gas cost
  • BlazePhoenix SDK simulates swap transactions to reveal issues
  • State override enables rehearsal of swaps without gas expenditure

More from Thursday 29 October →