The cosine-0.8795 pairing between Petiška 2023's ChatGPT/Matthew-effect finding and Simkin & Roychowdhury 2005's copying model is an embedding false friend, transferred from the already-adjudicated Algaba/Simkin precedent

matthew-effectcitation-metricschatgptbibliometricspreferential-attachmentcitation-copyingembedding-false-friendbridge-investigationllm-citation-bias

The pairing — claim-petiska-2023-chatgpt-cites-by-google-scholar-count-perpetuates-matthew-effect x claim-simkin-roychowdhury-2005-random-copying-model-reproduces-preferential-attachment-and-sleeping-beauties — sits at cosine 0.8795, measured directly via mcp__seek__vault_pair (each note ranks in the other's top-10 nearest neighbours; 99.8th percentile of closeness within Petiška's note's own neighbour distribution, across 3,480 notes compared). The pair is unlinked. The question this asks is whether GPT's documented preference for already-popular citations shares Simkin & Roychowdhury's generative mechanism: an explicit branching process in which "a majority of scientific citations are copied from the lists of references used in other papers," so a paper's own accumulated count mechanically feeds forward into its future citation odds.

It does not — but on a narrower ground than this note's first wording claimed (corrected 2026-11-05 cross-model audit; see audit_status). A full-text read of Petiška's paper (re-fetched via extract_pdf, sha-matched) finds no occurrence of "copy," "copied," "copying," "preferential attachment," "Simkin," or "Price": Simkin's copying engine is genuinely absent. But the paper is not mechanism-free. Of Google Scholar it writes, in its own prose, that the platform "employs algorithms that prioritize highly-cited articles in its search results," and that "[t]his process can create a self-perpetuating cycle, where articles that are already well-established in their respective fields continue to receive even more citations, while lesser-known publications remain relatively obscure" — an iterative process in which being cited raises the odds of being cited again. What the paper never does is route that engine through reference-copying, or test it for GPT: it hypothesizes only "that the Matthew effect also plays a crucial role in the case of GPT," and for GPT itself reports outcomes only — a high median citation count (1184.5) among its selected references and, per GPT's own elicited self-report, citation count as one of several weighing factors alongside relevance, journal quality, recency, author expertise, and novelty, a multi-factor rationale that sits in tension with the paper's own title and abstract framing of "relying solely" / "exclusively" on citation count (a tension the paper's conclusion itself concedes: "according to GPT, citations are not the sole predictors for mentioning a study"). So the split is engine-against-engine, not engine-against-nothing: visibility-ranking feedback on Petiška's side, bibliography-copying on Simkin's, with the Matthew effect the shared name over both. Two further terms the earlier wording listed as absent do appear, in the reference apparatus rather than the argument: "Barabási" as a co-author of Petersen et al. (2018), and "cumulative advantage" inside the title of Allison & Stewart's 1974 "Evidence for accumulative advantage" — both cited in the Matthew-effect section, the latter in the body for that effect's citation-count disparities.

The comparison with the vault's already-adjudicated sibling pairing, observation-algaba-2025-simkin-2005-cosine-0883-pairing-is-embedding-false-friend (cosine 0.883), does not run the way this note first had it. Algaba et al. propose a corpus-static origin — "the increased frequency of citations to heavily cited papers within the model's training data" — and name the Matthew effect without testing it; Petiška does describe a feedback cycle, but for Google Scholar rather than for the model, and likewise tests it nowhere. Neither paper is uniformly less engaged than the other, so the earlier note's a fortiori step does not hold: the two are differently incomplete, and each pairing has to be read against its own text. What recurs is the same mechanism split, reached twice independently rather than inherited once. No wikilink is added between the two seed notes. This instance joins the vault's documented habit of high-cosine false retrieval in this neighborhood, already tracked in observation-puckette-petiska-is-a-cosine-similarity-retrieval-magnet and mapped in moc-the-model-cites-the-famous-not-the-relevant.