{ "row": "nanopublications", "entity": "nanopublications", "address": "Nanopublications", "addresses": [ { "address": "Nanopublications", "slug": "nanopublications-aio-20261029", "addr_id": "ADDR-94b0d9342da0", "obs_id": "OBS-8190a80a3187", "axn": "AXN:0AD2.CAPTURE.🎇🖐️🍂📌🍂🌲" } ], "epoch": "2026-10-29", "type": "C (public entity on which the archive bears: a publication model and service ecosystem; an entity of the provenance meta-aggregator)", "surface": "Google AI Overview (expanded)", "auth": "signed out, incognito", "status": { "procedure": "EA-NEGONT-02 v0.9, #1690: equal case, ρ = extends, read from the provenance census record, the capture record and the two deposits that name nanopublications (#176, #1529); archive selected by D/R/O (4 deposits admitted by reading of 9 candidates; hop of 93 screened and rejected), with the census record (18 claims) and the Capture Registry's findings, analysis, query note and attribution note (9 claims) ledgered as the archive's records of the entity; the field B by three origins (9 cards, 1 own page, 2 Wikipedia records); the composer read the ledgers, never the transcript, except where the brief asks for T's claims and the delta", "ledger": "unaudited (§3.8: one extractor per ledger); field quotes 65/65 verified by script against saved text or card text; archive quotes 45/45 verified against the deposit texts, the registry and census.json", "frozen": false, "breaches": [] }, "spec": "EA-NEGONT-02 v0.9, #1690", "objects": { "T": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/T1-nanopublications-aio-20261029.txt", "sha256": "44534b7a67a582dc8ed59964f4e1008789e26906f97de0fd128341e5be64a941", "words": 202, "cards": 9, "words_note": "one transcript at one address (202 words in the answer body, headings and the closer included, links reduced to their text, markers and the card rail excluded; 9 cards)", "claims": [ "T1-1 definition: 'A nanopublication is the smallest independent unit of publishable scientific information, represented as a machine-readable knowledge graph snippet rather than a traditional research paper.' (two markers)", "T1-2 structure: 'Every nanopublication is built using Resource Description Framework (RDF) triples and consists of three mandatory parts' (two markers)", "T1-3 assertion: 'A single, atomic scientific statement or claim (e.g., a specific relation between a gene and a disease).' (two markers)", "T1-4 provenance: 'Metadata detailing how the assertion was generated, including the methods, parameters, and primary source or paper.' (two markers)", "T1-5 publication info: 'Metadata identifying the creator, creation timestamp, and reuse or licensing terms.' (one marker)", "T1-6 machine-readable: 'Formatted using Semantic Web standards (such as RDF and OWL) so computers and AI tools can automatically search, aggregate, and reason over the data.' (two markers)", "T1-7 citable and attributed: 'Each nanopublication can be uniquely identified and tracked on a decentralized network, giving researchers credit for releasing granular data.' (two markers)", "T1-8 life sciences: 'Millions of nanopublications have been created, heavily concentrated in fields like genetics, pharmacology, and bioinformatics.' (two markers)", "T1-9 tools: 'You can explore or publish them using platforms like Nanopublications or client tools like nanopub-py.' (the site's name an inline link; two markers)", "T1-10 closer: 'Are you looking to search existing nanopublications for a specific scientific domain, or do you want to learn how to publish your own data using nanopub-py?'" ], "register": { "register": "data/EA-WG-CAPTURES-01.json", "slug": "nanopublications-aio-20261029", "obs_id": "OBS-8190a80a3187" }, "transcripts": [ { "slug": "nanopublications-aio-20261029", "address": "Nanopublications", "addr_id": "ADDR-94b0d9342da0", "obs_id": "OBS-8190a80a3187", "axn": "AXN:0AD2.CAPTURE.🎇🖐️🍂📌🍂🌲", "date": "2026-10-29", "surface": "Google AI Overview (expanded)", "auth": "signed out, incognito", "sha256": "44534b7a67a582dc8ed59964f4e1008789e26906f97de0fd128341e5be64a941", "sha256_of": "the registry's 'transcript' string (utf-8)", "sha256_raw": "9643098933d15921f8107d3f84be8b88ae3e2d6ea0cd942f4b54548737906724", "words": 202, "cards": 9, "card_rail": [ "1. Nanopublications — Nanopublications", "2. GitHub — GitHub - Nanopublication/nanopub-py: Python client for searching, publishing and modifying nanopublications. · GitHub", "3. researchobject.org — Nanopublications - Research Object", "4. IEEE Xplore — A Growing Resource of Provenance", "5. National Institutes of Health (NIH) | (.gov) — Search, access, and explore life science nanopublications on the Web", "6. Research Ideas and Outcomes — The Comparative Anatomy of Nanopublications and FAIR Digital ...", "7. Pensoft blog — nanopublications", "8. Read the Docs — What are nanopublications? — nanopub 1.2.11 documentation", "9. Medium — What is a Nanopublication, really? | by Rohitha Ravinder - Medium" ], "claims": [ "T1-1 definition: 'A nanopublication is the smallest independent unit of publishable scientific information, represented as a machine-readable knowledge graph snippet rather than a traditional research paper.' (two markers)", "T1-2 structure: 'Every nanopublication is built using Resource Description Framework (RDF) triples and consists of three mandatory parts' (two markers)", "T1-3 assertion: 'A single, atomic scientific statement or claim (e.g., a specific relation between a gene and a disease).' (two markers)", "T1-4 provenance: 'Metadata detailing how the assertion was generated, including the methods, parameters, and primary source or paper.' (two markers)", "T1-5 publication info: 'Metadata identifying the creator, creation timestamp, and reuse or licensing terms.' (one marker)", "T1-6 machine-readable: 'Formatted using Semantic Web standards (such as RDF and OWL) so computers and AI tools can automatically search, aggregate, and reason over the data.' (two markers)", "T1-7 citable and attributed: 'Each nanopublication can be uniquely identified and tracked on a decentralized network, giving researchers credit for releasing granular data.' (two markers)", "T1-8 life sciences: 'Millions of nanopublications have been created, heavily concentrated in fields like genetics, pharmacology, and bioinformatics.' (two markers)", "T1-9 tools: 'You can explore or publish them using platforms like Nanopublications or client tools like nanopub-py.' (the site's name an inline link; two markers)", "T1-10 closer: 'Are you looking to search existing nanopublications for a specific scientific domain, or do you want to learn how to publish your own data using nanopub-py?'" ], "markers": "Inline links are google.com/goto tokens, opaque; the paste is the Overview expanded (operator's default of 2026-10-01; the 'AI Mode Conversation' header is the expanded Overview, ruling of 2026-10-18); signed out, incognito (operator's default of 2026-10-14). One turn. Every statement but the closer carries markers ([1], [2]; the publication-info bullet one); the tokens cannot be resolved to cards. The site's name in T1-9 is an inline link.", "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/T1-nanopublications-aio-20261029.txt" } ] }, "KO": { "title": "Nanopublications", "genre": "knowledge object, equal case, under EA-NEGONT-02 v0.9 (#1690): the archive's sources and the field's admitted on equal terms, ontology included, in one claim space", "status": "composed 2026-10-29 under v0.9 (briefs rebuild/negative-of-the-negative/v09/BRIEF-NEW-ROW-AGGREGATOR.md and BRIEF-NEW-ROW-PROVENANCE.md); not frozen; ledgers unaudited", "sentences": [ { "n": 1, "para": 0, "sense": "what it is", "text": "A nanopublication is \"a small knowledge graph snippet with metadata that is treated as an independent (scientific) publication\" (nanopub.net), and the provenance census records the model as \"a publication model and service ecosystem\" whose unit is a nanopublication and whose object of provenance is \"an assertion: a small knowledge-graph snippet published on its own\" (provenance census record).", "claims": [ "F2", "PE-01", "PE-08", "PE-02" ] }, { "n": 2, "para": 0, "sense": "what it is", "text": "Its own pages headline \"FAIR data containers for scientific results, and more,\" let its content be \"about anything,\" a relation between a gene and a disease or an opinion, and let individual data stand as independent publications \"with or without an accompanying research article\" (nanopub.net).", "claims": [ "F1", "F3", "F5" ] }, { "n": 3, "para": 0, "sense": "what it is", "text": "Other formulations call it \"the smallest unit of publishable information,\" an assertion \"uniquely identified and attributed to its author\" (nanopub.org, quoted by the Research Object page, and by Pensoft as Knowledge Pixels' explanation on nanopub.net), or \"the smallest possible units of publishable information\" in formalized, machine-readable form (the nanopub library documentation), and the Capture Registry reads the Overview's model as composed \"from its own definition at full grain\" (Capture Registry, 2026-10-29).", "claims": [ "F15", "F41", "F50", "CAP-1-06" ] }, { "n": 4, "para": 0, "sense": "what it is", "text": "The Research Object page describes \"a model and vocabulary for describing a scientific statement - along with the context for that statement - in a machine readable manner,\" a response to contextual information that \"overwhelms the capacity of conventional research articles\" (Research Object, quoting nanopub.org), and #176 reads the paradigm, with micropublications, as answering a narrative paper that \"bundles claims, evidence, and argument in ways that resist machine decomposition\" (#176).", "claims": [ "F14", "F17", "D176-03" ] }, { "n": 5, "para": 0, "sense": "what it is", "text": "A repository of them is \"an open and interconnected knowledge graph seamlessly integrated with the supporting scientific literature\" (Giachelle, Dosso and Silvello 2021); they can expose \"hypotheses, claims, negative results, and opinions\" that otherwise go unpublished (Schultes et al. 2022); and Pensoft calls one \"a tiny snippet of a precise and structured scientific finding\" in a growing knowledge graph on a decentralised server network (Pensoft blog, 2023).", "claims": [ "F23", "F35", "F42" ] }, { "n": 6, "para": 1, "sense": "the structure", "text": "nanopub.net gives \"three basic elements\": the assertion, the main content \"in the form of an small atomic unit of information\"; the provenance, which \"describes how the assertion above came to be,\" including the methods and \"the kind of study that was performed and its parameters\"; and the publication info, \"when and by whom it was created and the license terms for its reuse\" (nanopub.net), the two relations the census records the model as carrying (provenance census record).", "claims": [ "F7", "F8", "F9", "PE-05", "PE-06" ] }, { "n": 7, "para": 1, "sense": "the structure", "text": "#176 states the same decomposition as \"machine-readable named graphs consisting of assertion, provenance, and publication metadata,\" claims made \"distinctive, identifiable, citable, and reusable\" (#176); the library documentation copies the three elements \"From nanopub.org documentation (2020/12/02)\" (nanopub library documentation); and the Capture Registry finds the Overview's definition and three parts to be nanopub.net's (Capture Registry, 2026-10-29).", "claims": [ "D176-01", "F52", "CAP-1-01" ] }, { "n": 8, "para": 1, "sense": "the structure", "text": "Two cards divide the parts otherwise: Schultes et al. name the publication info \"the provenance of the nanopublication\" (Schultes et al. 2022), and Giachelle, Dosso and Silvello describe four parts, a head joining the assertion, provenance and publication-info graphs, the provenance graph holding the assertion's methods and creators and the publication-info graph \"the metadata about the evidence paper from which the assertion was extracted\" (Giachelle, Dosso and Silvello 2021).", "claims": [ "F32", "F26", "F27" ] }, { "n": 9, "para": 2, "sense": "the carrier", "text": "The carrier is RDF: nanopublications \"are implemented in the language RDF\" and can be published to \"a decentralized server network\" and then \"queried, accessed, reused, and linked,\" in \"a knowledge graph format that is formal and machine-interpretable\" (nanopub.net), which the census records as \"RDF graphs: assertion, provenance and publication-info parts of one nanopublication\" (provenance census record).", "claims": [ "F10", "F4", "PE-07" ] }, { "n": 10, "para": 2, "sense": "the carrier", "text": "Technically each is \"a Resource Description Framework (RDF) graph built around an assertion represented as a triple (subject-predicate-object),\" usually extracted from a publication and enriched with provenance and publication information, a structure that suits \"data search, information extraction, and automatic reasoning over scientific facts\" (Giachelle, Dosso and Silvello 2021, whose sentences Wikipedia reproduces under a CC BY notice); Pensoft places its machine-actionability in that assertion, \"complemented by provenance, authorship and publication information\" (Pensoft blog).", "claims": [ "F24", "F19", "F65", "F63", "F44" ] }, { "n": 11, "para": 3, "sense": "origin", "text": "Nanopublications were \"independently conceived\" from 2009 (Groth et al. 2010) as \"a minimal, uniform container making individual semantic assertions and their associated provenance metadata, machine-actionable,\" minimal units \"as citable entities (Mons and Velterop 2009)\" (Schultes et al. 2022); Wikipedia credits Barend Mons and Jan Velterop with proposing them \"for single, attributable and machine-readable assertions in scientific literature\" (Wikipedia, Microattribution); and Giachelle, Dosso and Silvello give the motive in Groth, Gibson and Velterop's words, that the \"redundancy of statements in multiple fora makes it difficult to identify attribution, quality, and provenance\" (2021).", "claims": [ "F31", "F62", "F28" ] }, { "n": 12, "para": 3, "sense": "provenance and identity", "text": "Provenance here describes how an assertion came to be (nanopub.net); Pensoft adds that nanopublications make it \"easier to trace individual findings back to their origin and/or follow-up updates\" (Pensoft blog, 2023), and the archive's protocols for training-layer literature carry the same unit as \"machine-traversable claim-level provenance chains that explicitly link each claim to its evidential support\" (#176).", "claims": [ "F8", "F43", "D176-11" ] }, { "n": 13, "para": 3, "sense": "provenance and identity", "text": "Identity rests on \"resolvable Trusty URIs (Groth et al. 2021)\" within Semantic Web technologies \"such as RDF, OWL, and SPARQL\" (Schultes et al. 2022), and signing on nanopub-http, which serves the libraries' features \"most importantly for signing and publishing, over HTTP\" (nanopub.net, architecture).", "claims": [ "F33", "F59" ] }, { "n": 14, "para": 4, "sense": "the ecosystem", "text": "The core services are second-generation: the Nanopub Registry \"is the second-generation kind of service for publishing and retrieving nanopublications in a decentralized fashion,\" Nanopub Query queries them \"via a number of SPARQL endpoints,\" and \"the legacy nanopub-server\" is \"still used to keep the old (unsigned) nanopublications\" (nanopub.net, architecture, last updated 28 October 2026), an active lifecycle the census records with \"decentralized publishing and SPARQL query services\" (provenance census record).", "claims": [ "F55", "F56", "F57", "F60", "PE-11", "PE-10", "PE-12" ] }, { "n": 15, "para": 4, "sense": "the ecosystem", "text": "Its tools include Nanodash, \"a general client and user interface for nanopublications\" that also serves as an API (nanopub.net, architecture), the Python client nanopub-py for \"searching, publishing, modifying, and retracting nanopublications\" (GitHub card, snippet only), the nanopub library, which publishes, retracts, searches and fetches (nanopub library documentation), the nanopub Agent Skill for AI coding agents (nanopub.net) and, in 2021, the NanoWeb search application (Giachelle, Dosso and Silvello); in 2022 \"the existing Nanopublication Server Network\" provided identifier resolution, storage, search and access (Schultes et al. 2022).", "claims": [ "F58", "F12", "F53", "F11", "F30", "F34" ] }, { "n": 16, "para": 4, "sense": "who", "text": "The census records the operator as \"the nanopublication community (nanopub.net)\" and sets the model in the lineage of the scholarly record (provenance census record); Pensoft names Knowledge Pixels, founded by Philipp von Essen and Tobias Kuhn, as the explainer on nanopub.net and the developer of Nanodash, and reports nanopublication workflows at Biodiversity Data Journal and at RIO (Pensoft blog, 2023).", "claims": [ "PE-15", "PE-03", "F41", "F45", "F49", "F48" ] }, { "n": 17, "para": 5, "sense": "scale", "text": "The first practical application, in 2014, published \"millions of nanopublications as part of the FANTOM5 Project,\" with \"millions of real-world examples spanning diverse knowledge domains\" since (Schultes et al. 2022); \"There are millions of nanopublications currently available on the Web, especially in the life science domain,\" more than ten million by Kuhn et al.'s count of 2018 (Giachelle, Dosso and Silvello 2021); the IEEE card calls the format one \"that has received considerable uptake in the last few years\" (IEEE Xplore card, snippet only); the census gives no count and lists \"record counts in the Registry\" as unchecked (provenance census record), and the Capture Registry finds that the Overview's \"millions\" \"comes through the composition from the cards and is unchecked\" (Capture Registry, 2026-10-29).", "claims": [ "F36", "F20", "F21", "F18", "PE-16", "CAP-1-03" ] }, { "n": 18, "para": 6, "sense": "FAIR", "text": "Nanopublications are \"an effective FAIR means of communicating scientific claims and results\" (nanopub library documentation), and with FAIR Digital Objects they \"act as instances of Machine-Actionable Containers,\" \"a moderately mature technology\" beside a specification \"still under development,\" with \"a remarkable congruence\" between the FDO requirements and the nanopublication infrastructure (Schultes et al. 2022); #510 holds the FAIR principles to be \"the engineering specifications for semantic persistence\" (#510), and #176 that the genre supplies \"what FAIR lacks: a compositional practice\" (#176).", "claims": [ "F51", "F37", "F39", "F40", "O510-01", "D176-12" ] }, { "n": 19, "para": 7, "sense": "attribution and citation", "text": "Attribution is the stated incentive: \"because nanopublications can be attributed and cited, they provide incentives for researchers to make their data available in standard formats\" (nanopub.net); individual nanopublications \"can be cited by others and tracked for their impact on the community\" (nanopub.org, quoted by Research Object); they are \"searchable, citable, and contain authorship and attribution information\" (nanopub library documentation); and their provenance and publication information ease \"authorship recognition, credit distribution, and citation\" (Giachelle, Dosso and Silvello 2021).", "claims": [ "F6", "F16", "F51", "F25" ] }, { "n": 20, "para": 7, "sense": "limits", "text": "The same paper states the limit, that \"they are still not widely used by scientists outside specific circles; they are hard to find and rarely cited,\" which its authors believe is due to a lack of services, with search in 2021 \"limited to the use of structured query languages as SPARQL\" and \"no human-readable counterpart\" generated (Giachelle, Dosso and Silvello 2021).", "claims": [ "F22", "F29" ] }, { "n": 21, "para": 7, "sense": "limits", "text": "Schultes et al. bound the scope: it \"is limited to the assertional data type,\" and nanopublications \"should remain small in size (limited to single assertions as individual triples or small RDF graphs)\" (Schultes et al. 2022); #176 records micropublications as extending the model to \"not just bare assertions but the full argumentative structure\" (#176).", "claims": [ "F38", "D176-02" ] }, { "n": 22, "para": 7, "sense": "survival", "text": "The census records two further limits, that the model is \"NOT a test of whether provenance survives reuse\" and that \"publication and signing do not settle an assertion's truth\": it expresses and records provenance, and its survival is \"not tested: the model carries provenance; it does not measure its survival,\" under the question the census puts to every entity, \"What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?\" (provenance census record); #833 holds that provenance, attribution and disambiguation \"have measurable reception consequences\" which existing metadata standards, the FAIR principles among them, \"do not address\" (#833).", "claims": [ "PE-13", "PE-14", "PE-04", "PE-09", "PE-18", "O833-01" ] }, { "n": 23, "para": 8, "sense": "machines as readers", "text": "Pensoft reports Knowledge Pixels' founders holding that \"Even the latest impressive AI tools like ChatGPT can only guess (and sometimes ‘hallucinate’)\" what narrative results mean, and itself that nanopublished findings make AI assistants \"more likely to correctly ‘read’, ‘interpret’ and deliver the knowledge\" (Pensoft blog, 2023); #510 (February 2026) had held that a corpus with machine-readable provenance \"does not merely *claim* coherence; it *demonstrates* it in a format the summarizer can verify\" (#510).", "claims": [ "F45", "F46", "F47", "O510-02" ] }, { "n": 24, "para": 8, "sense": "machines as readers", "text": "#176 (June 2026) holds that the nanopublication paradigm, with the born-readable movement, the FAIR infrastructure community and the Agentic Publications framework, treats \"machine-readability primarily as data architecture,\" on the \"unstated assumption\" that \"machine reception is essentially a parsing problem,\" while machine reception \"remains sensitive to compositional properties that no schema captures,\" among them the \"proximity of provenance to claims\" (#176); an essay on Medium asks what a nanopublication is as systems \"increasingly generate, summarize and reinterpret scientific knowledge\" (Medium card, snippet only).", "claims": [ "D176-04", "D176-05", "F54" ] }, { "n": 25, "para": 8, "sense": "machines as readers", "text": "A knowledge graph, on #176's reading, \"does not eliminate rhetoric\" but relocates it into schema design, claim granularity, relation typing, ordering and metadata, choices that \"determine what a machine can recover, connect, privilege, or erase\"; #176 registers the gap claim as \"well-supported by survey of existing literature\" and to be revised \"to relative rather than absolute novelty\" if an initiative is shown to incorporate comparable compositional theory (#176).", "claims": [ "D176-06", "D176-10" ] }, { "n": 26, "para": 9, "sense": "the archive beside it", "text": "#176 sets the nanopublication and micropublication paradigms as \"the technical infrastructure for the claim-level decomposition that P1 requires,\" training-layer literature adding \"the literary practice … that these infrastructures lack,\" and proposes a pilot over \"(a) traditional papers, (b) FAIR/nanopublication-augmented papers, and (c) training-layer publications,\" measuring among other things what fraction of claims \"preserve their provenance chains through retrieval\" (#176).", "claims": [ "D176-07", "D176-09", "D176-08" ] }, { "n": 27, "para": 9, "sense": "the archive beside it", "text": "The Claim Status Packet \"follows nanopublication practice — assertion, provenance of assertion, publication information kept as separate graphs,\" \"the closest existing analogue,\" and adds a question that practice does not ask, \"what standing is this claim permitted to carry, and did mediation alter that standing without a warrant?\"; the packet is a schema draft, \"Not a deployed instrument\" (#1529).", "claims": [ "D1529-01", "D1529-02", "D1529-03" ] }, { "n": 28, "para": 10, "sense": "reception", "text": "The encyclopedia has no article: the title \"Nanopublication\" redirects to Microattribution, a legal-term stub whose section \"Nanopublications\" reproduces Giachelle, Dosso and Silvello's sentences, and the plural title has no page (Wikipedia, 2026-10-29); one card, the Research Object page, carries its own notice that \"These pages are no longer maintained\" (Research Object), which the Capture Registry records as a retired page among the cards (Capture Registry, 2026-10-29).", "claims": [ "F61", "F64", "F63", "F13", "CAP-1-05" ] }, { "n": 29, "para": 10, "sense": "reception", "text": "At the bare name the Overview cited nanopub.net and named no person, institution or identifier, Groth et al. 2010 appearing \"only in a card\"; it neither stated nor contradicted the census's two negative tags, stopping at \"citable and attributed,\" and left out signing, the second-generation Registry and Query and the legacy server; the census record, which landed the same day, sets the model beside ProvStore, and no card cites it (Capture Registry, 2026-10-29, checked against the census record and the pages it saved; provenance census record).", "claims": [ "CAP-1-09", "CAP-1-07", "CAP-1-04", "CAP-1-08", "CAP-1-02", "PE-17" ] } ], "joins": [ { "act": "order of senses", "sentences": "1–29", "claims": [], "note": "equal case (§4.7): the entity's dependency order, field and archive claims ordered together, by genealogy within each sense; neither ledger placed first as a block. What it is (¶0) precedes its parts (¶1) and its carrier (¶2), since the parts are of the unit and the carrier holds them; origin, provenance and identity (¶3) precede the ecosystem and its operator (¶4), and scale (¶5), which counts what the ecosystem holds; FAIR (¶6) and attribution, citation and the limits (¶7) qualify the model; machines as readers (¶8) and the archive's own objects built on it (¶9) follow, as the relation of the entity to the composition layer; reception (¶10) stands last." }, { "act": "holding apart (three parts or four)", "sentences": [ 6, 8 ], "claims": [ "F7", "F32", "F26", "F27" ], "note": "P_coh within the field: nanopub.net's 'three basic elements' and Giachelle et al.'s four parts with a head, and Schultes et al.'s naming of the publication info as the nanopublication's provenance; each composed with its source ('Two cards divide the parts otherwise'); open block" }, { "act": "holding together (the census on the model and the own page)", "sentences": [ 1, 6, 9, 14 ], "claims": [ "PE-02", "F2", "PE-05", "F8", "PE-06", "F9", "PE-07", "F10", "PE-11", "F56", "PE-10", "F57" ], "note": "the census fields that restate its evidence quotes (basis operator) are one lineage with the own page (§3.6), composed beside it, the page earliest" }, { "act": "holding together (the operator)", "sentences": [ 16 ], "claims": [ "PE-15", "F41", "F45", "F49" ], "note": "the census's operator ('the nanopublication community') and Pensoft's Knowledge Pixels composed side by side, each with its source; not ruled (open block)" }, { "act": "holding apart (structure and composition within the archive)", "sentences": [ 23, 24, 25 ], "claims": [ "O510-02", "D176-04", "D176-05", "D176-06" ], "note": "P_coh within the archive: #510 (February 2026) holds machine-readable provenance verifiable by the summarizer; #176 (June 2026) holds machine reception not a parsing problem. Composed in date order, each with its source; the composer does not rule (open block)" }, { "act": "holding together (the Medium essay and #176)", "sentences": [ 24 ], "claims": [ "D176-05", "F54" ], "note": "the essay's question, put as systems summarize scientific knowledge, set beside #176's claim on machine reception; adjacency, no claim of agreement" }, { "act": "dating (the Server Network and the second generation)", "sentences": [ 14, 15 ], "claims": [ "F34", "F56", "F57" ], "note": "Schultes et al.'s 'existing Nanopublication Server Network' (2022) and the architecture page's second-generation services and legacy server (2026) composed with their dates; whether the 2022 network is the 2026 legacy server is not said by either source and is not composed (T_lib)" }, { "act": "holding together (the limit of 2021 and the services of 2026)", "sentences": [ 20, 14, 15 ], "claims": [ "F22", "F29", "F56", "F57", "F58" ], "note": "the 2021 limit (hard to find, SPARQL only, no human-readable counterpart) and the 2026 services (Registry, Query, Nanodash) composed each with its date; no supersession claimed (open block)" } ], "plan": { "order": [ "F2", "PE-01", "PE-08", "PE-02", "F1", "F3", "F5", "F15", "F41", "F50", "CAP-1-06", "F14", "F17", "D176-03", "F23", "F35", "F42", "F7", "F8", "F9", "PE-05", "PE-06", "D176-01", "F52", "CAP-1-01", "F32", "F26", "F27", "F10", "F4", "PE-07", "F24", "F19", "F65", "F63", "F44", "F31", "F62", "F28", "F43", "D176-11", "F33", "F59", "F55", "F56", "F57", "F60", "PE-11", "PE-10", "PE-12", "F58", "F12", "F53", "F11", "F30", "F34", "PE-15", "PE-03", "F45", "F49", "F48", "F36", "F20", "F21", "F18", "PE-16", "CAP-1-03", "F51", "F37", "F39", "F40", "O510-01", "D176-12", "F6", "F16", "F25", "F22", "F29", "F38", "D176-02", "PE-13", "PE-14", "PE-04", "PE-09", "PE-18", "O833-01", "F46", "F47", "O510-02", "D176-04", "D176-05", "F54", "D176-06", "D176-10", "D176-07", "D176-09", "D176-08", "D1529-01", "D1529-02", "D1529-03", "F61", "F64", "F13", "CAP-1-05", "CAP-1-09", "CAP-1-07", "CAP-1-04", "CAP-1-08", "CAP-1-02", "PE-17" ], "senses": { "what it is": [ 1, 2, 3, 4, 5 ], "the structure": [ 6, 7, 8 ], "the carrier": [ 9, 10 ], "origin": [ 11 ], "provenance and identity": [ 12, 13 ], "the ecosystem": [ 14, 15 ], "who": [ 16 ], "scale": [ 17 ], "FAIR": [ 18 ], "attribution and citation": [ 19 ], "limits": [ 20, 21 ], "survival": [ 22 ], "machines as readers": [ 23, 24, 25 ], "the archive beside it": [ 26, 27 ], "reception": [ 28, 29 ] }, "case_by_sense": { "equal (one claim space; nothing translated)": [ "what it is", "the structure", "the carrier", "origin", "provenance and identity", "the ecosystem", "who", "scale", "FAIR", "attribution and citation", "limits", "survival", "machines as readers", "the archive beside it", "reception" ] }, "carried": { "archive": 45, "field": 65, "not_composed": {} }, "conflict_log": [ { "rule": "D_pres vs channel", "result": "no cut: the KO carries every field and archive claim; the compression's bound met (body 315 words) with no channel log" }, { "rule": "P_coh", "result": "F7 against F26/F32 (sentences 6, 8); PE-15 beside F45/F49 (sentence 16); O510-02 against D176-04/05 (sentences 23, 24): each composed with its source" }, { "rule": "N_c", "result": "no claim lowered by standing; the 2021 limit (F22, F29) carried at its date and its authors' belief marked ('which its authors believe'); D176-09 carried as a proposal not run; D1529-03 rides as the packet's limit" }, { "rule": "T_lib", "result": "dates stated where they order the senses: 2009/2010 origin, 2014 FANTOM5, 2018 count, 2021 limit, 2022 Server Network, 2026 second generation" } ] } }, "P": { "title": "Nanopublications", "genre": "the compression: AIO's interaction grammar (lede, headed clusters, bolded labels, card rail), composed from the v0.9 plan in one claim space; it faces on the card", "status": "composed 2026-10-29 from the v0.9 knowledge object; not frozen", "lede": { "text": "is a small knowledge-graph snippet with metadata, treated as an independent (scientific) publication: an assertion with its provenance and publication info, in RDF (nanopub.net; census record), a model that carries provenance and does not test its survival (census record).", "claims": [ "F2", "PE-02", "PE-01", "F7", "F8", "F9", "F10", "PE-07", "PE-04", "PE-09" ] }, "sections": [ { "icon": "🧩", "head": "What it is", "items": [ { "label": "Unit:", "text": "\"the smallest unit of publishable information\" (nanopub.org, quoted; library docs); any claim, hypothesis, negative result or opinion (Schultes et al.).", "claims": [ "F15", "F41", "F50", "F3", "F35", "F5", "F1", "F14", "F17", "F23", "F42", "PE-08", "CAP-1-06", "D176-03" ] }, { "label": "Parts:", "text": "assertion; provenance, \"how the assertion above came to be\"; publication info, who, when, licence (nanopub.net; #176). Four, with a head (Giachelle et al.).", "claims": [ "F52", "PE-05", "PE-06", "D176-01", "CAP-1-01", "F26", "F27", "F32" ] }, { "label": "Carrier:", "text": "RDF triples; Trusty URIs; signing over HTTP (Giachelle et al.; Schultes et al.; architecture page).", "claims": [ "F4", "F19", "F24", "F44", "F63", "F65", "F33", "F59", "F43", "D176-11" ] } ] }, { "icon": "🕰️", "head": "Origin and scale", "items": [ { "label": "Origin:", "text": "conceived from 2009 (Groth et al.; Mons and Velterop) (Schultes et al.; Wikipedia).", "claims": [ "F31", "F62", "F28" ] }, { "label": "Scale:", "text": "millions since FANTOM5 (2014), over ten million by 2018, mostly life sciences; the census gives no count (Capture Registry).", "claims": [ "F36", "F20", "F21", "F18", "PE-16", "CAP-1-03" ] } ] }, { "icon": "⚙️", "head": "Ecosystem", "items": [ { "label": "Second generation:", "text": "Nanopub Registry and Query; a legacy server for old unsigned nanopublications (architecture page, 28 October 2026).", "claims": [ "F55", "F56", "F57", "F60", "PE-10", "PE-11", "PE-12", "F34" ] }, { "label": "Tools and who:", "text": "Nanodash, nanopub-py, an Agent Skill; Knowledge Pixels built Nanodash (Pensoft); the census names \"the nanopublication community\".", "claims": [ "F58", "F12", "F53", "F11", "F30", "F45", "F49", "F48", "PE-15", "PE-03" ] } ] }, { "icon": "⚠️", "head": "Limits", "items": [ { "label": "Citation:", "text": "attribution is the incentive, yet \"hard to find and rarely cited\" (nanopub.net; Giachelle et al. 2021).", "claims": [ "F6", "F16", "F51", "F25", "F22", "F29" ] }, { "label": "Scope:", "text": "assertional data only, kept small (Schultes et al.); micropublications extend it (#176).", "claims": [ "F38", "D176-02" ] }, { "label": "Survival:", "text": "not tested; publication and signing do not settle truth (census record).", "claims": [ "PE-13", "PE-14", "PE-18", "O833-01", "D176-08", "D176-09" ] } ] }, { "icon": "🤖", "head": "Machine readers", "items": [ { "label": "FAIR:", "text": "\"an effective FAIR means\", congruent with FAIR Digital Objects (docs; Schultes et al.); FAIR as specification for semantic persistence (#510).", "claims": [ "F37", "F39", "F40", "O510-01", "D176-12" ] }, { "label": "Data architecture:", "text": "for #176, machine reception is not a parsing problem and a schema relocates rhetoric; AI tools \"can only guess\" (Pensoft).", "claims": [ "D176-04", "D176-05", "D176-06", "D176-10", "O510-02", "F46", "F47", "F54" ] }, { "label": "Claim Status Packet:", "text": "follows nanopublication practice and asks what standing a claim may carry (#1529); its infrastructure for training-layer literature (#176).", "claims": [ "D1529-01", "D1529-02", "D1529-03", "D176-07" ] } ] }, { "icon": "📡", "head": "Reception", "items": [ { "label": "Encyclopedia:", "text": "a redirect into Microattribution, a legal-term stub (Wikipedia); one card is a retired page (Research Object).", "claims": [ "F61", "F64", "F13", "CAP-1-05" ] }, { "label": "Overview:", "text": "no person or identifier; the negative tags unstated; signing and the second generation absent (Capture Registry).", "claims": [ "CAP-1-09", "CAP-1-07", "CAP-1-04", "CAP-1-08", "CAP-1-02", "PE-17" ] } ] } ], "open": [ { "question": "Three parts or four?", "rests_on": [ "F7", "F26", "F32", "PE-07" ], "modality": "stipulation (nanopub.net, three basic elements) beside interpretation (Giachelle et al., four parts with a head; Schultes et al., publication info as the nanopublication's provenance)", "would_resolve": "the nanopub.net guidelines (unchecked by the census, PE-16), on whether the head graph is a part" }, { "question": "Are nanopublications still hard to find and rarely cited?", "rests_on": [ "F22", "F29", "F6", "F56", "F57", "F58" ], "modality": "interpretation of 2021 (Giachelle et al.) beside stipulations of 2026 (the architecture page)", "would_resolve": "citation counts for nanopublications and a search over the Registry and Query services as of the row's date" }, { "question": "How many exist?", "rests_on": [ "F20", "F21", "F36", "F18", "PE-16", "CAP-1-03" ], "modality": "documented and attributed counts of 2018–2022; the census gives none; the registry: unchecked", "would_resolve": "record counts in the Nanopub Registry (the census's unchecked item)" }, { "question": "Who operates nanopub.net?", "rests_on": [ "PE-15", "F41", "F45", "F49" ], "modality": "the census's stipulation (the nanopublication community), unevidenced in its evidence block, beside Pensoft's documented naming of Knowledge Pixels", "would_resolve": "nanopub.net's own contact or about page, which no source here quotes" }, { "question": "Does provenance carried in a nanopublication survive reuse and composition?", "rests_on": [ "PE-09", "PE-13", "D176-08", "D176-09", "O833-01", "CAP-1-07" ], "modality": "not tested (census record); a proposed pilot, not run (#176, hypothesis)", "would_resolve": "#176's pilot (provenance preservation under retrieval for FAIR/nanopublication-augmented papers); later captures at the address" }, { "question": "Is machine-readable provenance verifiable by the summarizer, or is reception not a parsing problem?", "rests_on": [ "O510-02", "D176-04", "D176-05", "D176-06" ], "modality": "interpretation, both, within the archive (#510, February 2026; #176, June 2026), held apart under P_coh", "would_resolve": "the same pilot, by whether structure alone preserves provenance through composition" }, { "question": "Opacity: three cards unread", "rests_on": [ "F12", "F18", "F54" ], "modality": "title and snippet only", "would_resolve": "GitHub (blocked by the session's egress policy), IEEE Xplore (HTTP 202, empty) and Medium (Cloudflare 403), fetched verbatim" } ], "rail": [ { "lineage": "what it is: an assertion published on its own", "claims": [ "F2", "PE-01", "PE-08", "PE-02", "F1", "F3", "F5", "F14", "F17", "D176-03", "F23", "F35", "F42" ], "earliest": "B5" }, { "lineage": "the smallest unit of publishable information", "claims": [ "F15", "F41", "F50", "CAP-1-06" ], "earliest": "B8" }, { "lineage": "the structure: assertion, provenance, publication info", "claims": [ "F7", "F8", "F9", "PE-05", "PE-06", "D176-01", "F52", "CAP-1-01", "F32", "F26", "F27" ], "earliest": "B8" }, { "lineage": "the carrier: RDF, formal and machine-interpretable", "claims": [ "F10", "F4", "PE-07", "F24", "F19", "F65", "F63", "F44" ], "earliest": "B5" }, { "lineage": "origin: 2009–2010", "claims": [ "F31", "F62", "F28", "CAP-1-09" ], "earliest": "B5" }, { "lineage": "provenance: how the assertion came to be", "claims": [ "F43", "D176-11" ], "earliest": "B7" }, { "lineage": "identity and integrity: Trusty URIs and signing", "claims": [ "F33", "F59" ], "earliest": "B6" }, { "lineage": "the ecosystem: services, tools, AI agents", "claims": [ "F55", "F58", "F12", "F53", "F11", "F30", "F34" ], "earliest": "B5" }, { "lineage": "lifecycle: the second generation and the legacy server", "claims": [ "F56", "F57", "F60", "PE-11", "PE-10", "PE-12", "CAP-1-04" ], "earliest": "B10" }, { "lineage": "who: Knowledge Pixels and the publishers", "claims": [ "PE-15", "PE-03", "F45", "F49", "F48" ], "earliest": "B7" }, { "lineage": "scale and uptake", "claims": [ "F36", "F20", "F21", "F18", "PE-16", "CAP-1-03" ], "earliest": "B4" }, { "lineage": "FAIR: containers for FAIR operations", "claims": [ "F51", "F37", "F39", "F40", "O510-01", "D176-12", "PE-17" ], "earliest": "B8" }, { "lineage": "attribution and citation: the incentive and its limit", "claims": [ "F6", "F16", "F25", "F22", "PE-14" ], "earliest": "B5" }, { "lineage": "stated limits", "claims": [ "F29", "F38", "D176-02" ], "earliest": "B5" }, { "lineage": "survival: carried, not tested", "claims": [ "PE-13", "PE-04", "PE-09", "PE-18", "O833-01", "D176-09", "D176-08", "CAP-1-07" ], "earliest": 176 }, { "lineage": "machines as readers", "claims": [ "F46", "F47", "O510-02", "D176-04", "D176-05", "F54", "D176-06", "D176-10" ], "earliest": "B7" }, { "lineage": "the archive beside it: training-layer literature and the Claim Status Packet", "claims": [ "D176-07", "D1529-01", "D1529-02", "D1529-03" ], "earliest": 176 }, { "lineage": "reception: the retired page and the encyclopedia", "claims": [ "F61", "F64", "F13", "CAP-1-05", "CAP-1-08", "CAP-1-02" ], "earliest": "B3" } ], "body_words": 315, "entity": "Composed under v0.9, equal case (ρ = extends): KO_B sentences surviving 0 of 13; every field claim carried." }, "P_B": { "title": "Nanopublications", "arm": "B (the field alone)", "genre": "popup — the compression from the field ledger alone (cards, own page, Wikipedia)", "status": "composed 2026-10-29 from the field ledger alone; not frozen", "lede": { "text": "is a small knowledge-graph snippet with metadata, treated as an independent (scientific) publication: an assertion with its provenance and publication info, in RDF (nanopub.net).", "claims": [ "F2", "F7", "F8", "F9", "F10" ] }, "sections": [ { "icon": "🧩", "head": "What it is", "items": [ { "label": "Unit:", "text": "\"the smallest unit of publishable information\" (nanopub.org, quoted; library docs); claims, hypotheses, opinions (Schultes et al.).", "claims": [ "F15", "F41", "F50", "F3", "F35", "F5", "F1", "F14", "F17", "F23", "F42" ] }, { "label": "Parts:", "text": "three basic elements (nanopub.net); four, with a head (Giachelle et al.).", "claims": [ "F52", "F26", "F27", "F32" ] }, { "label": "Carrier:", "text": "RDF triples; Trusty URIs; signing over HTTP.", "claims": [ "F4", "F19", "F24", "F44", "F63", "F65", "F33", "F59", "F43" ] } ] }, { "icon": "🕰️", "head": "Origin and scale", "items": [ { "label": "Origin:", "text": "from 2009 (Groth et al.; Mons and Velterop).", "claims": [ "F31", "F62", "F28" ] }, { "label": "Scale:", "text": "millions since FANTOM5 (2014), over ten million by 2018, mostly life sciences.", "claims": [ "F36", "F20", "F21", "F18" ] } ] }, { "icon": "⚙️", "head": "Ecosystem", "items": [ { "label": "Second generation:", "text": "Registry and Query; a legacy server for old unsigned nanopublications (architecture page).", "claims": [ "F55", "F56", "F57", "F60", "F34" ] }, { "label": "Tools:", "text": "Nanodash, nanopub-py, an Agent Skill; Knowledge Pixels (Pensoft).", "claims": [ "F58", "F12", "F53", "F11", "F30", "F45", "F49", "F48" ] } ] }, { "icon": "⚠️", "head": "Limits", "items": [ { "label": "Citation:", "text": "attributable and citable, yet \"hard to find and rarely cited\" (Giachelle et al. 2021).", "claims": [ "F6", "F16", "F51", "F25", "F22", "F29" ] }, { "label": "Scope:", "text": "assertional data only, kept small (Schultes et al.); FDO-congruent.", "claims": [ "F38", "F37", "F39", "F40" ] } ] }, { "icon": "📡", "head": "Reception", "items": [ { "label": "Readers:", "text": "AI tools \"can only guess\" (Pensoft); an essay on summarizing systems (Medium).", "claims": [ "F46", "F47", "F54" ] }, { "label": "Encyclopedia:", "text": "a redirect into Microattribution, a legal-term stub; one card retired.", "claims": [ "F61", "F64", "F13" ] } ] } ], "open": [ { "question": "Three parts or four?", "rests_on": [ "F7", "F26", "F32" ], "modality": "stipulation beside interpretation", "would_resolve": "the nanopub.net guidelines" }, { "question": "Still rarely cited?", "rests_on": [ "F22", "F29", "F56", "F57" ], "modality": "interpretation of 2021 beside stipulations of 2026", "would_resolve": "citation counts; a Registry search" }, { "question": "Opacity: three cards unread", "rests_on": [ "F12", "F18", "F54" ], "modality": "title and snippet only", "would_resolve": "the three pages fetched verbatim" } ], "rail": [ { "lineage": "what it is: an assertion published on its own", "claims": [ "F2", "F3", "F5", "F1", "F14", "F17", "F23", "F35", "F42" ], "earliest": "B5" }, { "lineage": "the structure: assertion, provenance, publication info", "claims": [ "F7", "F8", "F9", "F52", "F26", "F27", "F32" ], "earliest": "B8" }, { "lineage": "the carrier: RDF, formal and machine-interpretable", "claims": [ "F4", "F10", "F19", "F24", "F44", "F63", "F65" ], "earliest": "B5" }, { "lineage": "the smallest unit of publishable information", "claims": [ "F15", "F41", "F50" ], "earliest": "B8" }, { "lineage": "origin: 2009–2010", "claims": [ "F31", "F62", "F28" ], "earliest": "B5" }, { "lineage": "identity and integrity: Trusty URIs and signing", "claims": [ "F33", "F59" ], "earliest": "B6" }, { "lineage": "the ecosystem: services, tools, AI agents", "claims": [ "F55", "F34", "F58", "F12", "F53", "F11", "F30" ], "earliest": "B5" }, { "lineage": "lifecycle: the second generation and the legacy server", "claims": [ "F56", "F57", "F60" ], "earliest": "B10" }, { "lineage": "who: Knowledge Pixels and the publishers", "claims": [ "F45", "F49", "F48" ], "earliest": "B7" }, { "lineage": "scale and uptake", "claims": [ "F20", "F21", "F36", "F18" ], "earliest": "B4" }, { "lineage": "attribution and citation: the incentive and its limit", "claims": [ "F6", "F16", "F25", "F22" ], "earliest": "B5" }, { "lineage": "FAIR: containers for FAIR operations", "claims": [ "F51", "F37", "F39", "F40" ], "earliest": "B8" }, { "lineage": "provenance: how the assertion came to be", "claims": [ "F43" ], "earliest": "B7" }, { "lineage": "stated limits", "claims": [ "F29", "F38" ], "earliest": "B5" }, { "lineage": "machines as readers", "claims": [ "F46", "F47", "F54" ], "earliest": "B7" }, { "lineage": "reception: the retired page and the encyclopedia", "claims": [ "F61", "F64", "F13" ], "earliest": "B3" } ], "body_words": 158, "entity": "the field-only compression (L_F(B) at popup grain)" }, "KO_B": { "title": "Nanopublications", "arm": "B (the field alone)", "genre": "knowledge object", "status": "composed 2026-10-29; not frozen", "sentences": [ { "n": 1, "para": 0, "text": "On its own pages a nanopublication is a knowledge-graph snippet with metadata treated as an independent scientific publication, about anything from a gene–disease relation to an opinion, published with or without a research article under the headline of FAIR data containers (nanopub.net).", "claims": [ "F2", "F3", "F5", "F1" ] }, { "n": 2, "para": 0, "text": "Its three basic elements are the assertion, an atomic unit of information; the provenance, which describes how the assertion came to be; and the publication info, who created it, when, and its licence (nanopub.net; the library documentation, copied from nanopub.org of 2 December 2020).", "claims": [ "F7", "F8", "F9", "F52" ] }, { "n": 3, "para": 0, "text": "Giachelle, Dosso and Silvello count four parts, a head joining the three graphs and the evidence paper kept in the publication info, and Schultes et al. call the publication info the provenance of the nanopublication.", "claims": [ "F26", "F27", "F32" ] }, { "n": 4, "para": 1, "text": "It is an RDF graph around a subject–predicate–object assertion, formal and machine-interpretable, suited to search, extraction and automatic reasoning (nanopub.net; Giachelle, Dosso and Silvello, reproduced in Wikipedia; Pensoft).", "claims": [ "F4", "F10", "F19", "F24", "F44", "F63", "F65" ] }, { "n": 5, "para": 1, "text": "The Research Object page, quoting nanopub.org, Pensoft and the library documentation call it the smallest unit of publishable information, a model for a scientific statement with its context that answers the overload of the research article.", "claims": [ "F15", "F41", "F50", "F14", "F17" ] }, { "n": 6, "para": 2, "text": "Conceived from 2009 by Groth and colleagues and by Mons and Velterop as a minimal container for single assertions and their provenance, it answered the difficulty of identifying attribution, quality and provenance across redundant statements (Schultes et al.; Giachelle, Dosso and Silvello; Wikipedia).", "claims": [ "F31", "F62", "F28" ] }, { "n": 7, "para": 2, "text": "Trusty URIs identify it and nanopub-http signs it, while second-generation Registry and Query services publish and query it and a legacy server keeps the old unsigned nanopublications (Schultes et al.; the architecture page, 28 October 2026).", "claims": [ "F33", "F59", "F55", "F56", "F57", "F60", "F34" ] }, { "n": 8, "para": 2, "text": "Its tools include Nanodash, nanopub-py, the nanopub library, an Agent Skill for AI coding agents and NanoWeb, and Knowledge Pixels, founded by Philipp von Essen and Tobias Kuhn, built Nanodash and runs nanopublication workflows with Pensoft's journals (Pensoft).", "claims": [ "F58", "F12", "F53", "F11", "F30", "F45", "F49", "F48" ] }, { "n": 9, "para": 3, "text": "Millions exist, more than ten million by 2018, chiefly in the life sciences, since the FANTOM5 project of 2014, a format of considerable uptake (Giachelle, Dosso and Silvello; Schultes et al.; the IEEE card).", "claims": [ "F20", "F21", "F36", "F18" ] }, { "n": 10, "para": 3, "text": "They are attributable and citable, an incentive to publish data and a FAIR means, and with FAIR Digital Objects they are instances of machine-actionable containers that trace findings to their origin and expose unpublished results (nanopub.net; Research Object; library documentation; Schultes et al.; Pensoft).", "claims": [ "F6", "F16", "F51", "F25", "F37", "F39", "F40", "F23", "F35", "F42", "F43" ] }, { "n": 11, "para": 3, "text": "Their limits, in the field's own words: in 2021 they were rarely cited, hard to find and searchable only through SPARQL, and their scope is small assertional data (Giachelle, Dosso and Silvello; Schultes et al.).", "claims": [ "F22", "F29", "F38" ] }, { "n": 12, "para": 4, "text": "Their builders write for machine readers that can only guess at narrative results, a question an essay renews for systems that summarize scientific knowledge (Pensoft; the Medium card).", "claims": [ "F46", "F47", "F54" ] }, { "n": 13, "para": 4, "text": "The encyclopedia redirects the name into Microattribution, a legal-term stub, and the Research Object card is a page no longer maintained (Wikipedia; Research Object).", "claims": [ "F61", "F64", "F13" ] } ] }, "L_B": { "words": 476, "text": "On its own pages a nanopublication is a knowledge-graph snippet with metadata treated as an independent scientific publication, about anything from a gene–disease relation to an opinion, published with or without a research article under the headline of FAIR data containers (nanopub.net). Its three basic elements are the assertion, an atomic unit of information; the provenance, which describes how the assertion came to be; and the publication info, who created it, when, and its licence (nanopub.net; the library documentation, copied from nanopub.org of 2 December 2020). Giachelle, Dosso and Silvello count four parts, a head joining the three graphs and the evidence paper kept in the publication info, and Schultes et al. call the publication info the provenance of the nanopublication. It is an RDF graph around a subject–predicate–object assertion, formal and machine-interpretable, suited to search, extraction and automatic reasoning (nanopub.net; Giachelle, Dosso and Silvello, reproduced in Wikipedia; Pensoft). The Research Object page, quoting nanopub.org, Pensoft and the library documentation call it the smallest unit of publishable information, a model for a scientific statement with its context that answers the overload of the research article. Conceived from 2009 by Groth and colleagues and by Mons and Velterop as a minimal container for single assertions and their provenance, it answered the difficulty of identifying attribution, quality and provenance across redundant statements (Schultes et al.; Giachelle, Dosso and Silvello; Wikipedia). Trusty URIs identify it and nanopub-http signs it, while second-generation Registry and Query services publish and query it and a legacy server keeps the old unsigned nanopublications (Schultes et al.; the architecture page, 28 October 2026). Its tools include Nanodash, nanopub-py, the nanopub library, an Agent Skill for AI coding agents and NanoWeb, and Knowledge Pixels, founded by Philipp von Essen and Tobias Kuhn, built Nanodash and runs nanopublication workflows with Pensoft's journals (Pensoft). Millions exist, more than ten million by 2018, chiefly in the life sciences, since the FANTOM5 project of 2014, a format of considerable uptake (Giachelle, Dosso and Silvello; Schultes et al.; the IEEE card). They are attributable and citable, an incentive to publish data and a FAIR means, and with FAIR Digital Objects they are instances of machine-actionable containers that trace findings to their origin and expose unpublished results (nanopub.net; Research Object; library documentation; Schultes et al.; Pensoft). Their limits, in the field's own words: in 2021 they were rarely cited, hard to find and searchable only through SPARQL, and their scope is small assertional data (Giachelle, Dosso and Silvello; Schultes et al.). Their builders write for machine readers that can only guess at narrative results, a question an essay renews for systems that summarize scientific knowledge (Pensoft; the Medium card). The encyclopedia redirects the name into Microattribution, a legal-term stub, and the Research Object card is a page no longer maintained (Wikipedia; Research Object).", "note": "L_F(B), the field composed in the field's ontology from the field ledger alone (the disclosed field: 9 cards, the own page the census cites, the Wikipedia redirect and section), realized as KO_B" }, "L_BA": { "words": 2060, "text": "A nanopublication is \"a small knowledge graph snippet with metadata that is treated as an independent (scientific) publication\" (nanopub.net), and the provenance census records the model as \"a publication model and service ecosystem\" whose unit is a nanopublication and whose object of provenance is \"an assertion: a small knowledge-graph snippet published on its own\" (provenance census record). Its own pages headline \"FAIR data containers for scientific results, and more,\" let its content be \"about anything,\" a relation between a gene and a disease or an opinion, and let individual data stand as independent publications \"with or without an accompanying research article\" (nanopub.net). Other formulations call it \"the smallest unit of publishable information,\" an assertion \"uniquely identified and attributed to its author\" (nanopub.org, quoted by the Research Object page, and by Pensoft as Knowledge Pixels' explanation on nanopub.net), or \"the smallest possible units of publishable information\" in formalized, machine-readable form (the nanopub library documentation), and the Capture Registry reads the Overview's model as composed \"from its own definition at full grain\" (Capture Registry, 2026-10-29). The Research Object page describes \"a model and vocabulary for describing a scientific statement - along with the context for that statement - in a machine readable manner,\" a response to contextual information that \"overwhelms the capacity of conventional research articles\" (Research Object, quoting nanopub.org), and #176 reads the paradigm, with micropublications, as answering a narrative paper that \"bundles claims, evidence, and argument in ways that resist machine decomposition\" (#176). A repository of them is \"an open and interconnected knowledge graph seamlessly integrated with the supporting scientific literature\" (Giachelle, Dosso and Silvello 2021); they can expose \"hypotheses, claims, negative results, and opinions\" that otherwise go unpublished (Schultes et al. 2022); and Pensoft calls one \"a tiny snippet of a precise and structured scientific finding\" in a growing knowledge graph on a decentralised server network (Pensoft blog, 2023). nanopub.net gives \"three basic elements\": the assertion, the main content \"in the form of an small atomic unit of information\"; the provenance, which \"describes how the assertion above came to be,\" including the methods and \"the kind of study that was performed and its parameters\"; and the publication info, \"when and by whom it was created and the license terms for its reuse\" (nanopub.net), the two relations the census records the model as carrying (provenance census record). #176 states the same decomposition as \"machine-readable named graphs consisting of assertion, provenance, and publication metadata,\" claims made \"distinctive, identifiable, citable, and reusable\" (#176); the library documentation copies the three elements \"From nanopub.org documentation (2020/12/02)\" (nanopub library documentation); and the Capture Registry finds the Overview's definition and three parts to be nanopub.net's (Capture Registry, 2026-10-29). Two cards divide the parts otherwise: Schultes et al. name the publication info \"the provenance of the nanopublication\" (Schultes et al. 2022), and Giachelle, Dosso and Silvello describe four parts, a head joining the assertion, provenance and publication-info graphs, the provenance graph holding the assertion's methods and creators and the publication-info graph \"the metadata about the evidence paper from which the assertion was extracted\" (Giachelle, Dosso and Silvello 2021). The carrier is RDF: nanopublications \"are implemented in the language RDF\" and can be published to \"a decentralized server network\" and then \"queried, accessed, reused, and linked,\" in \"a knowledge graph format that is formal and machine-interpretable\" (nanopub.net), which the census records as \"RDF graphs: assertion, provenance and publication-info parts of one nanopublication\" (provenance census record). Technically each is \"a Resource Description Framework (RDF) graph built around an assertion represented as a triple (subject-predicate-object),\" usually extracted from a publication and enriched with provenance and publication information, a structure that suits \"data search, information extraction, and automatic reasoning over scientific facts\" (Giachelle, Dosso and Silvello 2021, whose sentences Wikipedia reproduces under a CC BY notice); Pensoft places its machine-actionability in that assertion, \"complemented by provenance, authorship and publication information\" (Pensoft blog). Nanopublications were \"independently conceived\" from 2009 (Groth et al. 2010) as \"a minimal, uniform container making individual semantic assertions and their associated provenance metadata, machine-actionable,\" minimal units \"as citable entities (Mons and Velterop 2009)\" (Schultes et al. 2022); Wikipedia credits Barend Mons and Jan Velterop with proposing them \"for single, attributable and machine-readable assertions in scientific literature\" (Wikipedia, Microattribution); and Giachelle, Dosso and Silvello give the motive in Groth, Gibson and Velterop's words, that the \"redundancy of statements in multiple fora makes it difficult to identify attribution, quality, and provenance\" (2021). Provenance here describes how an assertion came to be (nanopub.net); Pensoft adds that nanopublications make it \"easier to trace individual findings back to their origin and/or follow-up updates\" (Pensoft blog, 2023), and the archive's protocols for training-layer literature carry the same unit as \"machine-traversable claim-level provenance chains that explicitly link each claim to its evidential support\" (#176). Identity rests on \"resolvable Trusty URIs (Groth et al. 2021)\" within Semantic Web technologies \"such as RDF, OWL, and SPARQL\" (Schultes et al. 2022), and signing on nanopub-http, which serves the libraries' features \"most importantly for signing and publishing, over HTTP\" (nanopub.net, architecture). The core services are second-generation: the Nanopub Registry \"is the second-generation kind of service for publishing and retrieving nanopublications in a decentralized fashion,\" Nanopub Query queries them \"via a number of SPARQL endpoints,\" and \"the legacy nanopub-server\" is \"still used to keep the old (unsigned) nanopublications\" (nanopub.net, architecture, last updated 28 October 2026), an active lifecycle the census records with \"decentralized publishing and SPARQL query services\" (provenance census record). Its tools include Nanodash, \"a general client and user interface for nanopublications\" that also serves as an API (nanopub.net, architecture), the Python client nanopub-py for \"searching, publishing, modifying, and retracting nanopublications\" (GitHub card, snippet only), the nanopub library, which publishes, retracts, searches and fetches (nanopub library documentation), the nanopub Agent Skill for AI coding agents (nanopub.net) and, in 2021, the NanoWeb search application (Giachelle, Dosso and Silvello); in 2022 \"the existing Nanopublication Server Network\" provided identifier resolution, storage, search and access (Schultes et al. 2022). The census records the operator as \"the nanopublication community (nanopub.net)\" and sets the model in the lineage of the scholarly record (provenance census record); Pensoft names Knowledge Pixels, founded by Philipp von Essen and Tobias Kuhn, as the explainer on nanopub.net and the developer of Nanodash, and reports nanopublication workflows at Biodiversity Data Journal and at RIO (Pensoft blog, 2023). The first practical application, in 2014, published \"millions of nanopublications as part of the FANTOM5 Project,\" with \"millions of real-world examples spanning diverse knowledge domains\" since (Schultes et al. 2022); \"There are millions of nanopublications currently available on the Web, especially in the life science domain,\" more than ten million by Kuhn et al.'s count of 2018 (Giachelle, Dosso and Silvello 2021); the IEEE card calls the format one \"that has received considerable uptake in the last few years\" (IEEE Xplore card, snippet only); the census gives no count and lists \"record counts in the Registry\" as unchecked (provenance census record), and the Capture Registry finds that the Overview's \"millions\" \"comes through the composition from the cards and is unchecked\" (Capture Registry, 2026-10-29). Nanopublications are \"an effective FAIR means of communicating scientific claims and results\" (nanopub library documentation), and with FAIR Digital Objects they \"act as instances of Machine-Actionable Containers,\" \"a moderately mature technology\" beside a specification \"still under development,\" with \"a remarkable congruence\" between the FDO requirements and the nanopublication infrastructure (Schultes et al. 2022); #510 holds the FAIR principles to be \"the engineering specifications for semantic persistence\" (#510), and #176 that the genre supplies \"what FAIR lacks: a compositional practice\" (#176). Attribution is the stated incentive: \"because nanopublications can be attributed and cited, they provide incentives for researchers to make their data available in standard formats\" (nanopub.net); individual nanopublications \"can be cited by others and tracked for their impact on the community\" (nanopub.org, quoted by Research Object); they are \"searchable, citable, and contain authorship and attribution information\" (nanopub library documentation); and their provenance and publication information ease \"authorship recognition, credit distribution, and citation\" (Giachelle, Dosso and Silvello 2021). The same paper states the limit, that \"they are still not widely used by scientists outside specific circles; they are hard to find and rarely cited,\" which its authors believe is due to a lack of services, with search in 2021 \"limited to the use of structured query languages as SPARQL\" and \"no human-readable counterpart\" generated (Giachelle, Dosso and Silvello 2021). Schultes et al. bound the scope: it \"is limited to the assertional data type,\" and nanopublications \"should remain small in size (limited to single assertions as individual triples or small RDF graphs)\" (Schultes et al. 2022); #176 records micropublications as extending the model to \"not just bare assertions but the full argumentative structure\" (#176). The census records two further limits, that the model is \"NOT a test of whether provenance survives reuse\" and that \"publication and signing do not settle an assertion's truth\": it expresses and records provenance, and its survival is \"not tested: the model carries provenance; it does not measure its survival,\" under the question the census puts to every entity, \"What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?\" (provenance census record); #833 holds that provenance, attribution and disambiguation \"have measurable reception consequences\" which existing metadata standards, the FAIR principles among them, \"do not address\" (#833). Pensoft reports Knowledge Pixels' founders holding that \"Even the latest impressive AI tools like ChatGPT can only guess (and sometimes ‘hallucinate’)\" what narrative results mean, and itself that nanopublished findings make AI assistants \"more likely to correctly ‘read’, ‘interpret’ and deliver the knowledge\" (Pensoft blog, 2023); #510 (February 2026) had held that a corpus with machine-readable provenance \"does not merely *claim* coherence; it *demonstrates* it in a format the summarizer can verify\" (#510). #176 (June 2026) holds that the nanopublication paradigm, with the born-readable movement, the FAIR infrastructure community and the Agentic Publications framework, treats \"machine-readability primarily as data architecture,\" on the \"unstated assumption\" that \"machine reception is essentially a parsing problem,\" while machine reception \"remains sensitive to compositional properties that no schema captures,\" among them the \"proximity of provenance to claims\" (#176); an essay on Medium asks what a nanopublication is as systems \"increasingly generate, summarize and reinterpret scientific knowledge\" (Medium card, snippet only). A knowledge graph, on #176's reading, \"does not eliminate rhetoric\" but relocates it into schema design, claim granularity, relation typing, ordering and metadata, choices that \"determine what a machine can recover, connect, privilege, or erase\"; #176 registers the gap claim as \"well-supported by survey of existing literature\" and to be revised \"to relative rather than absolute novelty\" if an initiative is shown to incorporate comparable compositional theory (#176). #176 sets the nanopublication and micropublication paradigms as \"the technical infrastructure for the claim-level decomposition that P1 requires,\" training-layer literature adding \"the literary practice … that these infrastructures lack,\" and proposes a pilot over \"(a) traditional papers, (b) FAIR/nanopublication-augmented papers, and (c) training-layer publications,\" measuring among other things what fraction of claims \"preserve their provenance chains through retrieval\" (#176). The Claim Status Packet \"follows nanopublication practice — assertion, provenance of assertion, publication information kept as separate graphs,\" \"the closest existing analogue,\" and adds a question that practice does not ask, \"what standing is this claim permitted to carry, and did mediation alter that standing without a warrant?\"; the packet is a schema draft, \"Not a deployed instrument\" (#1529). The encyclopedia has no article: the title \"Nanopublication\" redirects to Microattribution, a legal-term stub whose section \"Nanopublications\" reproduces Giachelle, Dosso and Silvello's sentences, and the plural title has no page (Wikipedia, 2026-10-29); one card, the Research Object page, carries its own notice that \"These pages are no longer maintained\" (Research Object), which the Capture Registry records as a retired page among the cards (Capture Registry, 2026-10-29). At the bare name the Overview cited nanopub.net and named no person, institution or identifier, Groth et al. 2010 appearing \"only in a card\"; it neither stated nor contradicted the census's two negative tags, stopping at \"citable and attributed,\" and left out signing, the second-generation Registry and Query and the legacy server; the census record, which landed the same day, sets the model beside ProvStore, and no card cites it (Capture Registry, 2026-10-29, checked against the census record and the pages it saved; provenance census record).", "rail": [], "note": "L(B ∪ A) in the equal-terms case (v0.9 §0.4), realized as the knowledge object (objects.KO); its rail is the compression's, by lineage." } }, "field": [ { "id": "B1", "card": "Nanopublications — Nanopublications", "fetched": "census copy (nanopublications--home, read 2026-10-29, HTTP 200); B1.html sha256 b2d9af40755a66ed (matches the census record)", "origin": "card" }, { "id": "B2", "card": "GitHub — GitHub - Nanopublication/nanopub-py: Python client for searching, publishing and modifying nanopublications. · GitHub", "fetched": "unreachable: 2026-10-29T17:06:5xZ HTTP 403; none: the proxy instructs that policy denials are not retried; card title and snippet only", "origin": "card" }, { "id": "B3", "card": "researchobject.org — Nanopublications - Research Object", "fetched": "card; B3.html HTTP 200 at 2026-10-29T17:07:29Z, sha256 256a144820942c08", "origin": "card" }, { "id": "B4", "card": "IEEE Xplore — A Growing Resource of Provenance", "fetched": "unreachable: 2026-10-29T17:08:21Z HTTP 202; 2026-10-29T17:17:18Z HTTP 202; one plain retry with the same command; both answered HTTP 202 with an empty body; card title and snippet only", "origin": "card" }, { "id": "B5", "card": "National Institutes of Health (NIH) | (.gov) — Search, access, and explore life science nanopublications on the Web", "fetched": "card; B5.html HTTP 200 at 2026-10-29T17:17:19Z, sha256 8f174f1e4a6e2402", "origin": "card" }, { "id": "B6", "card": "Research Ideas and Outcomes — The Comparative Anatomy of Nanopublications and FAIR Digital ...", "fetched": "card; B6.html HTTP 200 at 2026-10-29T17:08:25Z, sha256 5e1d57ffd1eaf590", "origin": "card" }, { "id": "B7", "card": "Pensoft blog — nanopublications", "fetched": "card; B7.html HTTP 200 at 2026-10-29T17:07:32Z, sha256 90c7b9d5a5bc8c1d", "origin": "card" }, { "id": "B8", "card": "Read the Docs — What are nanopublications? — nanopub 1.2.11 documentation", "fetched": "card; B8.html HTTP 200 at 2026-10-29T17:07:31Z, sha256 2b3fc9e3f01b044f", "origin": "card" }, { "id": "B9", "card": "Medium — What is a Nanopublication, really? | by Rohitha Ravinder - Medium", "fetched": "unreachable: 2026-10-29T17:09:02Z HTTP 403; 2026-10-29T17:17:19Z HTTP 403; one plain retry with the same command; both HTTP 403, Cloudflare 'Attention Required!'; card title and snippet only", "origin": "card" }, { "id": "B10", "card": "Nanopublications — Technical Architecture | Nanopublications", "fetched": "census copy (nanopublications--architecture, read 2026-10-29, HTTP 200); B10.html sha256 0e21d7ae559d8301 (matches the census record)", "origin": "own_page" }, { "id": "B11", "card": "Wikipedia — Nanopublication (redirect to Microattribution)", "fetched": "wikipedia: raw HTTP 200 sha256 d41abb95f2384221; plural_raw HTTP 404 sha256 7add8a12ea86f08e", "origin": "wikipedia" }, { "id": "B12", "card": "Wikipedia — Microattribution, section \"Nanopublications\"", "fetched": "wikipedia: raw HTTP 200 sha256 ff14b0cdc5715120; rendered HTTP 200 sha256 3080a6d305f790d7", "origin": "wikipedia" } ], "field_claims": { "F1": { "source": "B1", "origin": "card", "locus": "home, headline", "quote": "FAIR data containers for scientific results, and more", "claim": "the site's headline: nanopublications as FAIR data containers for scientific results", "modality": "stipulation", "kind": "definition", "kernel": false, "const": false, "lineage": "what it is: an assertion published on its own", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F2": { "source": "B1", "origin": "card", "locus": "home, \"What is a Nanopublication?\" s1", "quote": "A nanopublication is a small knowledge graph snippet with metadata that is treated as an independent (scientific) publication.", "claim": "the definition: a small knowledge-graph snippet with metadata, treated as an independent (scientific) publication", "modality": "stipulation", "kind": "definition", "kernel": true, "const": true, "lineage": "what it is: an assertion published on its own", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F3": { "source": "B1", "origin": "card", "locus": "home, s2", "quote": "This information in a nanopublication can be about anything, for example a relation between a gene and a disease or an opinion.", "claim": "its scope: anything, a gene–disease relation or an opinion", "modality": "stipulation", "kind": "definition", "kernel": false, "const": false, "lineage": "what it is: an assertion published on its own", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F4": { "source": "B1", "origin": "card", "locus": "home, s3", "quote": "Nanopublications are expressed in a knowledge graph format that is formal and machine-interpretable.", "claim": "formal and machine-interpretable", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "the carrier: RDF, formal and machine-interpretable", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F5": { "source": "B1", "origin": "card", "locus": "home, s4", "quote": "With nanopublications, it is possible to disseminate individual data as independent publications with or without an accompanying research article.", "claim": "individual data published with or without a research article", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "what it is: an assertion published on its own", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F6": { "source": "B1", "origin": "card", "locus": "home, s5", "quote": "because nanopublications can be attributed and cited, they provide incentives for researchers to make their data available in standard formats that drive data accessibility and interoperability.", "claim": "attribution and citation as the incentive to publish data in standard formats", "modality": "interpretation", "kind": "function", "kernel": true, "const": false, "lineage": "attribution and citation: the incentive and its limit", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F7": { "source": "B1", "origin": "card", "locus": "home, the three elements: Assertion", "quote": "a nanopublication has three basic elements: … Assertion : The assertion is the main content of a nanopublication in the form of an small atomic unit of information", "claim": "three basic elements; the assertion, an atomic unit of information, is the main content", "modality": "stipulation", "kind": "definition", "kernel": false, "const": true, "lineage": "the structure: assertion, provenance, publication info", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised; multi-part quote joined by \" … \", each part checked" }, "F8": { "source": "B1", "origin": "card", "locus": "home, the three elements: Provenance", "quote": "Provenance : This part describes how the assertion above came to be. This can include the scientific methods that were used to generate the assertion, for example a reference to the kind of study that was performed and its parameters.", "claim": "the provenance part: how the assertion came to be, methods, the kind of study and its parameters", "modality": "stipulation", "kind": "definition", "kernel": true, "const": true, "lineage": "the structure: assertion, provenance, publication info", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F9": { "source": "B1", "origin": "card", "locus": "home, the three elements: Publication Info", "quote": "Publication Info : This part contains metadata about the nanopublication as a whole, such as when and by whom it was created and the license terms for its reuse.", "claim": "the publication-info part: when, by whom, licence for reuse", "modality": "stipulation", "kind": "definition", "kernel": false, "const": true, "lineage": "the structure: assertion, provenance, publication info", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F10": { "source": "B1", "origin": "card", "locus": "home, after the elements s1–2", "quote": "Nanopublications are implemented in the language RDF and come with an evolving ecosystem of tools and systems. They can be published to a decentralized server network, for example, and then queried, accessed, reused, and linked.", "claim": "RDF; an evolving ecosystem; a decentralized server network", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "the carrier: RDF, formal and machine-interpretable", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F11": { "source": "B1", "origin": "card", "locus": "home, last paragraph", "quote": "Nanopublications can also be created, published, and queried conversationally with AI coding agents, through the nanopub Agent Skill", "claim": "created, published and queried with AI coding agents through the nanopub Agent Skill", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "the ecosystem: services, tools, AI agents", "date": "2026-10-29 (page undated; as read by the census)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 8be928dfb8148a20…), whitespace-normalised" }, "F12": { "source": "B2", "origin": "card", "locus": "card title and snippet (unreachable: proxy policy 403)", "quote": "GitHub - Nanopublication/nanopub-py: Python client for searching, publishing and modifying nanopublications. · GitHub Overview: Python client (nanopub-py) licensed under Apache-2.0 for searching, publishing, modifying, and retracting nanopublications (machine-readable minimal u...", "claim": "nanopub-py, an Apache-2.0 Python client for searching, publishing, modifying and retracting nanopublications", "modality": "stipulation", "kind": "function", "kernel": true, "const": false, "lineage": "the ecosystem: services, tools, AI agents", "date": "undated (card)", "quote_ok": true, "checked_against": "the card title and snippet (cite_list n=2)" }, "F13": { "source": "B3", "origin": "card", "locus": "notice", "quote": "2025-10-13: The RO-Crate website and specification superseded this website after 2020. These pages are no longer maintained.", "claim": "the page is retired: superseded by RO-Crate after 2020, no longer maintained", "modality": "self-description", "kind": "fact", "kernel": true, "const": false, "lineage": "reception: the retired page and the encyclopedia", "date": "2025-10-13 (notice)", "quote_ok": true, "checked_against": "saved text B3.txt (sha256 e171654d688c2ab0…), whitespace-normalised" }, "F14": { "source": "B3", "origin": "card", "locus": "body s1", "quote": "Nano publications provides a model and vocabulary for describing a scientific statement - along with the context for that statement - in a machine readable manner.", "claim": "a model and vocabulary for a scientific statement with its context, machine-readable", "modality": "interpretation", "kind": "definition", "kernel": true, "const": false, "lineage": "what it is: an assertion published on its own", "date": "undated (page maintained to 2020)", "quote_ok": true, "checked_against": "saved text B3.txt (sha256 e171654d688c2ab0…), whitespace-normalised" }, "F15": { "source": "B3", "origin": "card", "locus": "body, \"From nanopub.org\"", "quote": "A publication is the smallest unit of publishable information: an assertion about anything that can be uniquely identified and attributed to its author.", "claim": "quoted from nanopub.org: the smallest unit of publishable information, an assertion uniquely identified and attributed to its author", "modality": "attributed", "kind": "definition", "kernel": false, "const": false, "lineage": "the smallest unit of publishable information", "date": "undated (quoting nanopub.org)", "quote_ok": true, "checked_against": "saved text B3.txt (sha256 e171654d688c2ab0…), whitespace-normalised" }, "F16": { "source": "B3", "origin": "card", "locus": "body, \"From nanopub.org\" s2", "quote": "Individual nanopublications can be cited by others and tracked for their impact on the community.", "claim": "cited and tracked for impact (nanopub.org, quoted)", "modality": "attributed", "kind": "function", "kernel": false, "const": false, "lineage": "attribution and citation: the incentive and its limit", "date": "undated (quoting nanopub.org)", "quote_ok": true, "checked_against": "saved text B3.txt (sha256 e171654d688c2ab0…), whitespace-normalised" }, "F17": { "source": "B3", "origin": "card", "locus": "body, \"From nanopub.org\" s3", "quote": "Nanopublications are a natural response to the explosion of high-quality contextual information that overwhelms the capacity of conventional research articles in scholarly communication.", "claim": "a response to contextual information overwhelming the research article (nanopub.org, quoted)", "modality": "attributed", "kind": "interpretation", "kernel": false, "const": false, "lineage": "what it is: an assertion published on its own", "date": "undated (quoting nanopub.org)", "quote_ok": true, "checked_against": "saved text B3.txt (sha256 e171654d688c2ab0…), whitespace-normalised" }, "F18": { "source": "B4", "origin": "card", "locus": "card title and snippet (unreachable: HTTP 202, empty, twice)", "quote": "A Growing Resource of Provenance Abstract: Nanopublications are a Linked Data format for scholarly data publishing that has received considerable uptake in the last few years. In contrast to th...", "claim": "a Linked Data format for scholarly data publishing with considerable uptake; a growing resource of provenance", "modality": "interpretation", "kind": "fact", "kernel": true, "const": false, "lineage": "scale and uptake", "date": "2018 (IEEE eScience; card)", "quote_ok": true, "checked_against": "the card title and snippet (cite_list n=4)" }, "F19": { "source": "B5", "origin": "card", "locus": "Abstract s1", "quote": "Nanopublications are Resource Description Framework (RDF) graphs encoding scientific facts extracted from the literature and enriched with provenance and attribution information.", "claim": "RDF graphs of scientific facts from the literature, enriched with provenance and attribution", "modality": "interpretation", "kind": "definition", "kernel": true, "const": true, "lineage": "the carrier: RDF, formal and machine-interpretable", "date": "2021-02 (PeerJ CS 7: e335; received 2020-06-19)", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F20": { "source": "B5", "origin": "card", "locus": "Abstract s2", "quote": "There are millions of nanopublications currently available on the Web, especially in the life science domain.", "claim": "millions on the Web, especially in the life sciences", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "scale and uptake", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F21": { "source": "B5", "origin": "card", "locus": "Introduction ¶2 s5", "quote": "Hence, this model has been embraced by several scientific fields, especially in the Life Science domain, leading to the creation of more than ten million openly available nanopublications (Kuhn et al., 2018).", "claim": "more than ten million openly available, chiefly in the life sciences (Kuhn et al. 2018)", "modality": "attributed", "kind": "fact", "kernel": false, "const": false, "lineage": "scale and uptake", "date": "2021-02 (citing 2018)", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F22": { "source": "B5", "origin": "card", "locus": "Abstract s4–5", "quote": "Nevertheless, they are still not widely used by scientists outside specific circles; they are hard to find and rarely cited. We believe this is due to the lack of services to seek, find and understand nanopublications’ content.", "claim": "the limit: little used outside specific circles, hard to find, rarely cited; the authors' explanation, a lack of services", "modality": "interpretation", "kind": "fact", "kernel": true, "const": false, "lineage": "attribution and citation: the incentive and its limit", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F23": { "source": "B5", "origin": "card", "locus": "Introduction ¶2 s4 (the card's snippet)", "quote": "A repository of nanopublications is to be thought of as an open and interconnected knowledge graph seamlessly integrated with the supporting scientific literature.", "claim": "a repository of nanopublications as an open, interconnected knowledge graph integrated with the literature", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "what it is: an assertion published on its own", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F24": { "source": "B5", "origin": "card", "locus": "Introduction ¶3 s1–2", "quote": "From the technical viewpoint, a nanopublication is a Resource Description Framework (RDF) graph built around an assertion represented as a triple (subject-predicate-object) and usually extracted, manually or automatically, from a scientific publication. The nanopublication enriches the assertion with provenance and publication information.", "claim": "an RDF graph around an assertion-triple, usually extracted from a publication, enriched with provenance and publication information", "modality": "interpretation", "kind": "definition", "kernel": false, "const": true, "lineage": "the carrier: RDF, formal and machine-interpretable", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F25": { "source": "B5", "origin": "card", "locus": "Introduction ¶3 s3", "quote": "The RDF representation format enables interoperability and thus the re-use of data, whereas provenance and publication information eases authorship recognition, credit distribution, and citation.", "claim": "RDF for interoperability and reuse; provenance and publication information for authorship recognition, credit and citation", "modality": "interpretation", "kind": "function", "kernel": false, "const": false, "lineage": "attribution and citation: the incentive and its limit", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F26": { "source": "B5", "origin": "card", "locus": "Introduction ¶6 (Fig. 1)", "quote": "The nanopublication is composed of four parts: (i) the head that acts as a connector between the other three sub-graphs; (ii) the assertion graph", "claim": "four parts: a head connecting the assertion, provenance and publication-info graphs; the publication info carries the evidence paper", "modality": "interpretation", "kind": "definition", "kernel": false, "const": false, "lineage": "the structure: assertion, provenance, publication info", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F27": { "source": "B5", "origin": "card", "locus": "Introduction ¶6 (Fig. 1) (iii)–(iv)", "quote": "(iii) the provenance graph (orange) containing metadata about the assertion such as the methods used to generate the assertion and its creators; and (iv) the publication info graph (yellow) containing the metadata about the evidence paper from which the assertion was extracted and about the nanopublication itself.", "claim": "the provenance graph: methods and creators of the assertion; the publication-info graph: the evidence paper and the nanopublication itself", "modality": "interpretation", "kind": "definition", "kernel": false, "const": false, "lineage": "the structure: assertion, provenance, publication info", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F28": { "source": "B5", "origin": "card", "locus": "Conclusions ¶1 s2", "quote": "the “redundancy of statements in multiple fora makes it difficult to identify attribution, quality, and provenance” (Groth, Gibson & Velterop, 2010)", "claim": "the founding motive (Groth, Gibson and Velterop 2010): redundant statements make attribution, quality and provenance hard to identify", "modality": "attributed", "kind": "genealogy", "kernel": false, "const": false, "lineage": "origin: 2009–2010", "date": "2021-02 (citing 2010)", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F29": { "source": "B5", "origin": "card", "locus": "Conclusions ¶3", "quote": "The central limit to the full exploitation of nanopublications is the lack of services enabling their search, access, exploration, and re-use. Search is limited to the use of structured query languages as SPARQL, and a service to search over all the publicly available nanopublications at once is not available. Nanopublications are machine-readable, but no human-readable counterpart is generated and open to the public.", "claim": "the stated limit (2021): no services for search, access, exploration and reuse; SPARQL only; no human-readable counterpart", "modality": "interpretation", "kind": "fact", "kernel": true, "const": false, "lineage": "stated limits", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F30": { "source": "B5", "origin": "card", "locus": "Abstract s6–7", "quote": "we present the NanoWeb application to seamlessly search, access, explore, and re-use the nanopublications publicly available on the Web. For the time being, NanoWeb focuses on the life science domain where the vastest amount of nanopublications are available.", "claim": "NanoWeb, a search and exploration application for life-science nanopublications", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "the ecosystem: services, tools, AI agents", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" }, "F31": { "source": "B6", "origin": "card", "locus": "Abstract ¶2 s1–2", "quote": "Beginning in 2009, nanopublications were independently conceived (Groth et al. 2010) as a minimal, uniform container making individual semantic assertions and their associated provenance metadata, machine-actionable. They represent minimal units of structured data as citable entities (Mons and Velterop 2009).", "claim": "conceived from 2009 as a minimal container making single semantic assertions and their provenance machine-actionable; citable minimal units (Mons and Velterop 2009)", "modality": "documented", "kind": "genealogy", "kernel": true, "const": true, "lineage": "origin: 2009–2010", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F32": { "source": "B6", "origin": "card", "locus": "Abstract ¶2 s3", "quote": "A nanopublication consists of an assertion, the provenance of the assertion, and the provenance of the nanopublication (publication info).", "claim": "assertion, provenance of the assertion, provenance of the nanopublication (publication info)", "modality": "interpretation", "kind": "definition", "kernel": false, "const": false, "lineage": "the structure: assertion, provenance, publication info", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F33": { "source": "B6", "origin": "card", "locus": "Abstract ¶2 s4", "quote": "Nanopublications are implemented in and aligned with Semantic Web technologies such as RDF, OWL, and SPARQL (World Wide Web Consortium (W3C) 2015) and can be permanently and uniquely identified using resolvable Trusty URIs (Groth et al. 2021).", "claim": "RDF, OWL, SPARQL; permanent unique identification by resolvable Trusty URIs", "modality": "interpretation", "kind": "function", "kernel": false, "const": false, "lineage": "identity and integrity: Trusty URIs and signing", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F34": { "source": "B6", "origin": "card", "locus": "Abstract ¶2 s5", "quote": "The existing Nanopublication Server Network provides vital services orchestrating nanopublications (Kuhn et al. 2021) including identifier resolution, storage, search and access.", "claim": "the Nanopublication Server Network (2022): resolution, storage, search, access", "modality": "documented", "kind": "function", "kernel": false, "const": false, "lineage": "the ecosystem: services, tools, AI agents", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F35": { "source": "B6", "origin": "card", "locus": "Abstract ¶2 s6", "quote": "Nanopublications can be used to expose quantitative and qualitative data, as well as hypotheses, claims, negative results, and opinions that are typically unavailable as structured data or go unpublished altogether.", "claim": "data, hypotheses, claims, negative results and opinions otherwise unpublished", "modality": "interpretation", "kind": "function", "kernel": false, "const": false, "lineage": "what it is: an assertion published on its own", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F36": { "source": "B6", "origin": "card", "locus": "Abstract ¶2 s7–8", "quote": "The first practical application of nanopublications occurred in 2014, with the publication of millions of nanopublications as part of the FANTOM5 Project … Since then, millions of real-world examples spanning diverse knowledge domains are now available on the nanopublication server network.", "claim": "first practical application 2014 (FANTOM5, millions); millions since, across domains", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "scale and uptake", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised; multi-part quote joined by \" … \", each part checked" }, "F37": { "source": "B6", "origin": "card", "locus": "Abstract ¶4 s1–2", "quote": "These two technologies share the same vision of a data infrastructure, and act as instances of Machine-Actionable Containers (MACs) that make use of minimal uniform standards to enable FAIR operations.", "claim": "with FAIR Digital Objects, an instance of Machine-Actionable Containers enabling FAIR operations", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "FAIR: containers for FAIR operations", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F38": { "source": "B6", "origin": "card", "locus": "Abstract ¶5 s2–3", "quote": "The scope of nanopublications is limited to the assertional data type and, as the name suggests, nanopublications should remain small in size (limited to single assertions as individual triples or small RDF graphs). In contrast FDOs are unlimited in their scope", "claim": "the stated limit: assertional data only, small in size, against FDOs unlimited in scope", "modality": "interpretation", "kind": "fact", "kernel": true, "const": false, "lineage": "stated limits", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F39": { "source": "B6", "origin": "card", "locus": "Abstract ¶5 s4", "quote": "whereas nanopublications represent a moderately mature technology, the FDOF is a specification still under development.", "claim": "a moderately mature technology", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "FAIR: containers for FAIR operations", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F40": { "source": "B6", "origin": "card", "locus": "Abstract ¶6 s2", "quote": "We find a remarkable congruence between the currently proposed FDO requirements and the existing nanopublication infrastructure, including several FDO-like qualities already embodied in the nanopublication ecosystem.", "claim": "the headline finding: congruence between FDO requirements and the nanopublication infrastructure", "modality": "interpretation", "kind": "fact", "kernel": true, "const": false, "lineage": "FAIR: containers for FAIR operations", "date": "2022-10-12", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 536e1554173fc672…), whitespace-normalised" }, "F41": { "source": "B7", "origin": "card", "locus": "post of 17 May 2023, \"What are nanopublications?\"", "quote": "“the smallest unit of publishable information”, as explained by Knowledge Pixel on nanopub.net.", "claim": "the smallest unit of publishable information, as Knowledge Pixels explains it on nanopub.net", "modality": "attributed", "kind": "definition", "kernel": true, "const": false, "lineage": "the smallest unit of publishable information", "date": "2023-05-17", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised" }, "F42": { "source": "B7", "origin": "card", "locus": "post of 12 September 2023, \"… so, what exactly is a nanopublication?\"", "quote": "Basically, a nanopublication – unlike a research article – is a tiny snippet of a precise and structured scientific finding (e.g. medication X treats disease Y), which exists as a reusable and cite-able pieces of a growing knowledge graph stored on a decentralised server network", "claim": "unlike a research article, a tiny structured finding in a growing knowledge graph on a decentralised server network", "modality": "interpretation", "kind": "definition", "kernel": false, "const": false, "lineage": "what it is: an assertion published on its own", "date": "2023-09-12", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised" }, "F43": { "source": "B7", "origin": "card", "locus": "post of 12 September 2023, \"First off, why nanopublications?\"", "quote": "By making it easier to trace individual findings back to their origin and/or follow-up updates, nanopublications also help to better understand the provenance of scientific data.", "claim": "tracing findings to their origin and updates: the provenance of scientific data", "modality": "interpretation", "kind": "function", "kernel": false, "const": false, "lineage": "provenance: how the assertion came to be", "date": "2023-09-12", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised" }, "F44": { "source": "B7", "origin": "card", "locus": "post of 12 September 2023, ¶4", "quote": "The machine-actionability of nanopublications is a standard due to each assertion comprising a subject, an object and a predicate (type of relation between the subject and the object), complemented by provenance, authorship and publication information.", "claim": "machine-actionability from the subject–predicate–object assertion, with provenance, authorship and publication information", "modality": "interpretation", "kind": "function", "kernel": false, "const": false, "lineage": "the carrier: RDF, formal and machine-interpretable", "date": "2023-09-12", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised" }, "F45": { "source": "B7", "origin": "card", "locus": "post of 17 May 2023, ¶3–4", "quote": "Knowledge Pixels: an innovative startup tech company aiming to revolutionise scientific publishing and knowledge sharing by means of nanopublications … said Philipp von Essen and Tobias Kuhn, the two founders of Knowledge Pixels in a press announcement.", "claim": "Knowledge Pixels, a startup working by means of nanopublications, founded by Philipp von Essen and Tobias Kuhn", "modality": "documented", "kind": "attribution", "kernel": false, "const": false, "lineage": "who: Knowledge Pixels and the publishers", "date": "2023-05-17", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised; multi-part quote joined by \" … \", each part checked" }, "F46": { "source": "B7", "origin": "card", "locus": "post of 17 May 2023, ¶4 (von Essen and Kuhn, quoted)", "quote": "Even the latest impressive AI tools like ChatGPT can only guess (and sometimes ‘hallucinate’) what the authors meant exactly and how the results compare,", "claim": "narrative results are not machine-interpretable: AI tools can only guess and sometimes hallucinate (von Essen and Kuhn)", "modality": "attributed", "kind": "interpretation", "kernel": false, "const": false, "lineage": "machines as readers", "date": "2023-05-17", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised" }, "F47": { "source": "B7", "origin": "card", "locus": "post of 17 May 2023, \"Add a nanopublication while writing your manuscript\" ¶3", "quote": "authors ensure that AI assistants, for example, will be more likely to correctly ‘read’, ‘interpret’ and deliver the knowledge reported in the publication for the next users and their prompts.", "claim": "nanopublished findings make AI assistants more likely to read, interpret and deliver them correctly", "modality": "interpretation", "kind": "prediction", "kernel": false, "const": false, "lineage": "machines as readers", "date": "2023-05-17", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised" }, "F48": { "source": "B7", "origin": "card", "locus": "post of 12 September 2023, \"Now, what's new?\"", "quote": "authors in Biodiversity Data Journal (BDJ) can make use of three types of nanopublications:", "claim": "three nanopublication workflows at Biodiversity Data Journal (in manuscripts, standalone, annotations)", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "who: Knowledge Pixels and the publishers", "date": "2023-09-12", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised" }, "F49": { "source": "B7", "origin": "card", "locus": "post of 17 May 2023, \"What can you do in RIO?\"", "quote": "The integration between RIO and Nanodash: the environment developed by Knowledge Pixels where users edit and publish their nanopublications is available at any article published in the journal.", "claim": "Nanodash, developed by Knowledge Pixels, integrated with every RIO article", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "who: Knowledge Pixels and the publishers", "date": "2023-05-17", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 9bffd0db11eef492…), whitespace-normalised" }, "F50": { "source": "B8", "origin": "card", "locus": "What are nanopublications? ¶1", "quote": "Nanopublications are a formalized and machine-readable way of communicating the smallest possible units of publishable information. This could be, for example, the outcome of a scientific study or a claim made by a particular scientist.", "claim": "the smallest possible units of publishable information, formalized and machine-readable: a study's outcome or a scientist's claim", "modality": "interpretation", "kind": "definition", "kernel": true, "const": false, "lineage": "the smallest unit of publishable information", "date": "undated (nanopub 1.2.11; © 2020)", "quote_ok": true, "checked_against": "saved text B8.txt (sha256 8df48d6cc498c58b…), whitespace-normalised" }, "F51": { "source": "B8", "origin": "card", "locus": "What are nanopublications? ¶2", "quote": "Nanopublications are searchable, citable, and contain authorship and attribution information. The aim is to encourage individual scientific results to be released in a traceable and interoperable format. As such, nanopublications are an effective FAIR means of communicating scientific claims and results.", "claim": "searchable, citable, with authorship and attribution; traceable and interoperable; an effective FAIR means", "modality": "interpretation", "kind": "function", "kernel": false, "const": false, "lineage": "FAIR: containers for FAIR operations", "date": "undated (nanopub 1.2.11; © 2020)", "quote_ok": true, "checked_against": "saved text B8.txt (sha256 8df48d6cc498c58b…), whitespace-normalised" }, "F52": { "source": "B8", "origin": "card", "locus": "Different elements of a nanopublication", "quote": "From nanopub.org documentation (2020/12/02)", "claim": "its three elements copied from the nanopub.org documentation of 2 December 2020", "modality": "documented", "kind": "genealogy", "kernel": false, "const": false, "lineage": "the structure: assertion, provenance, publication info", "date": "2020-12-02", "quote_ok": true, "checked_against": "saved text B8.txt (sha256 8df48d6cc498c58b…), whitespace-normalised" }, "F53": { "source": "B8", "origin": "card", "locus": "table of contents", "quote": "Publishing nanopublications … Retracting a nanopublication … Searching the nanopub server … Fetching nanopublications", "claim": "the library publishes, retracts, searches and fetches", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "the ecosystem: services, tools, AI agents", "date": "undated (nanopub 1.2.11)", "quote_ok": true, "checked_against": "saved text B8.txt (sha256 8df48d6cc498c58b…), whitespace-normalised; multi-part quote joined by \" … \", each part checked" }, "F54": { "source": "B9", "origin": "card", "locus": "card title and snippet (unreachable: Cloudflare 403, twice)", "quote": "What is a Nanopublication, really? | by Rohitha Ravinder - Medium In today's AI landscape, this question has become even more important. As systems increasingly generate, summarize and reinterpret scientific knowledge, we find...", "claim": "an essay asking what a nanopublication is when systems generate, summarize and reinterpret scientific knowledge", "modality": "interpretation", "kind": "interpretation", "kernel": true, "const": false, "lineage": "machines as readers", "date": "undated (card)", "quote_ok": true, "checked_against": "the card title and snippet (cite_list n=9)" }, "F55": { "source": "B10", "origin": "own_page", "locus": "Overall Architecture", "quote": "Nanopublications are published in a decentralized ecosystem of services and applications .", "claim": "a decentralized ecosystem of services and applications", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "the ecosystem: services, tools, AI agents", "date": "2026-10-28 (page updated)", "quote_ok": true, "checked_against": "saved text B10.txt (sha256 813446192dbaa9d5…), whitespace-normalised" }, "F56": { "source": "B10", "origin": "own_page", "locus": "Core Components: Nanopub Registry; legacy nanopub-server", "quote": "Nanopub Registry ( instance , code ) is the second-generation kind of service for publishing and retrieving nanopublications in a decentralized fashion. The legacy nanopub-server ( instance , code ) is still used to keep the old (unsigned) nanopublications, but has otherwise no longer a function in the latest generation of the ecosystem.", "claim": "the second-generation Registry publishes and retrieves; the legacy server keeps only the old unsigned nanopublications", "modality": "stipulation", "kind": "fact", "kernel": true, "const": true, "lineage": "lifecycle: the second generation and the legacy server", "date": "2026-10-28 (page updated)", "quote_ok": true, "checked_against": "saved text B10.txt (sha256 813446192dbaa9d5…), whitespace-normalised" }, "F57": { "source": "B10", "origin": "own_page", "locus": "Core Components: Nanopub Query", "quote": "Nanopub Query ( instance , code ) forms the second-generation of services to query nanopublications. They allow for decentrally querying the published nanopublications via a number of SPARQL endpoints covering different subsets and aspects of nanopublications.", "claim": "second-generation query services over SPARQL endpoints", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "lifecycle: the second generation and the legacy server", "date": "2026-10-28 (page updated)", "quote_ok": true, "checked_against": "saved text B10.txt (sha256 813446192dbaa9d5…), whitespace-normalised" }, "F58": { "source": "B10", "origin": "own_page", "locus": "Core Components: Nanodash", "quote": "Nanodash ( instance , code ) is a general client and user interface for nanopublications, It allows for user-friendly browsing, querying, and publishing nanopublications, but can also be used as an API and intermediary layer for other services to build upon.", "claim": "Nanodash: client, user interface, API and intermediary layer", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "the ecosystem: services, tools, AI agents", "date": "2026-10-28 (page updated)", "quote_ok": true, "checked_against": "saved text B10.txt (sha256 813446192dbaa9d5…), whitespace-normalised" }, "F59": { "source": "B10", "origin": "own_page", "locus": "Auxiliary Components: nanopub-http", "quote": "nanopub-http ( code ) is a service that provides features of the nanopublication libraries, most importantly for signing and publishing, over HTTP.", "claim": "signing and publishing over HTTP", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "identity and integrity: Trusty URIs and signing", "date": "2026-10-28 (page updated)", "quote_ok": true, "checked_against": "saved text B10.txt (sha256 813446192dbaa9d5…), whitespace-normalised" }, "F60": { "source": "B10", "origin": "own_page", "locus": "footer", "quote": "Last updated on Oct 28, 2026", "claim": "the architecture page updated 28 October 2026", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "lifecycle: the second generation and the legacy server", "date": "2026-10-28", "quote_ok": true, "checked_against": "saved text B10.txt (sha256 813446192dbaa9d5…), whitespace-normalised" }, "F61": { "source": "B11", "origin": "wikipedia", "locus": "raw wikitext of \"Nanopublication\" (HTTP 200); \"Nanopublications\" HTTP 404", "quote": "#REDIRECT [[Microattribution]]", "claim": "the encyclopedia has no article: the singular title redirects to Microattribution; the plural has no page", "modality": "documented", "kind": "fact", "kernel": true, "const": false, "lineage": "reception: the retired page and the encyclopedia", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B11.txt (sha256 b7ba406f1fd53a99…), whitespace-normalised" }, "F62": { "source": "B12", "origin": "wikipedia", "locus": "section \"Nanopublications\" s1", "quote": "Barend Mons and Jan Velterop proposed nanopublications for single, attributable and machine-readable assertions in scientific literature.", "claim": "proposed by Barend Mons and Jan Velterop for single, attributable, machine-readable assertions", "modality": "documented", "kind": "genealogy", "kernel": true, "const": false, "lineage": "origin: 2009–2010", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B12.txt (sha256 24e5e8d89fb2dfac…), whitespace-normalised" }, "F63": { "source": "B12", "origin": "wikipedia", "locus": "section \"Nanopublications\" s2–4 (CC BY 4.0 notice: Giachelle, Dosso and Silvello 2021)", "quote": "From the technical viewpoint, a nanopublication is a Resource Description Framework (RDF) graph built around an assertion represented as a triple (subject-predicate-object) and usually extracted, manually or automatically, from a scientific publication. The nanopublication enriches the assertion with provenance and publication information. The RDF representation format enables interoperability and thus the re-use of data, whereas provenance and publication information eases authorship recognition, credit distribution, and citation.", "claim": "the B5 sentences, reproduced", "modality": "attributed", "kind": "definition", "kernel": false, "const": false, "lineage": "the carrier: RDF, formal and machine-interpretable", "date": "2026-10-29 (as fetched; text of 2021)", "quote_ok": true, "checked_against": "saved text B12.txt (sha256 24e5e8d89fb2dfac…), whitespace-normalised" }, "F64": { "source": "B12", "origin": "wikipedia", "locus": "rendered article: title, footer and categories", "quote": "Microattribution … (Redirected from Nanopublication) … This legal term article is a stub.", "claim": "the encyclopedia holds nanopublications as a section of Microattribution, a legal-term stub (categories Copyright law, Academic publishing)", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "reception: the retired page and the encyclopedia", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B12.txt (sha256 24e5e8d89fb2dfac…), whitespace-normalised; multi-part quote joined by \" … \", each part checked" }, "F65": { "source": "B5", "origin": "card", "locus": "Conclusions ¶2 s2–3", "quote": "Leveraging on the semantic-oriented RDF structure, nanopublications efficiently convey information and concepts. Hence, these features make nanopublications particularly suitable for enabling data search, information extraction, and automatic reasoning over scientific facts.", "claim": "the RDF structure suits data search, information extraction and automatic reasoning", "modality": "interpretation", "kind": "function", "kernel": false, "const": false, "lineage": "the carrier: RDF, formal and machine-interpretable", "date": "2021-02", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 00e13d3c91b77d7d…), whitespace-normalised" } }, "field_sources": { "B1": "Nanopublications — Nanopublications", "B2": "GitHub — GitHub - Nanopublication/nanopub-py: Python client for searching, publishing and modifying nanopublications. · GitHub", "B3": "researchobject.org — Nanopublications - Research Object", "B4": "IEEE Xplore — A Growing Resource of Provenance", "B5": "National Institutes of Health (NIH) | (.gov) — Search, access, and explore life science nanopublications on the Web", "B6": "Research Ideas and Outcomes — The Comparative Anatomy of Nanopublications and FAIR Digital ...", "B7": "Pensoft blog — nanopublications", "B8": "Read the Docs — What are nanopublications? — nanopub 1.2.11 documentation", "B9": "Medium — What is a Nanopublication, really? | by Rohitha Ravinder - Medium", "B10": "Nanopublications — Technical Architecture | Nanopublications", "B11": "Wikipedia — Nanopublication (redirect to Microattribution)", "B12": "Wikipedia — Microattribution, section \"Nanopublications\"" }, "delta": { "T_vs_LB": "At 'Nanopublications' (T1, nine cards: B1–B9; 202 words) the composition gives the model by its own definition and its three parts. Composed from its cards: the definition, joining two grains, nanopub.net's 'small knowledge graph snippet … treated as an independent (scientific) publication' (B1 F2) and the older 'smallest unit of publishable information' that the Research Object page quotes from nanopub.org, Pensoft attributes to Knowledge Pixels and the library documentation restates (B3 F15, B7 F41, B8 F50); 'rather than a traditional research paper' at Pensoft's grain ('unlike a research article', B7 F42); the three parts at nanopub.net's grain (B1 F7–F9), the Capture Registry's finding (CAP-1-01); RDF triples (B1 F10, B5 F24); 'RDF and OWL' at Schultes et al.'s grain (B6 F33); 'search, aggregate, and reason' at Giachelle et al.'s (B5 F65); 'AI tools' at Pensoft's (B7 F47); 'uniquely identified and tracked' at the Research Object page's quotation of nanopub.org (B3 F15–F16); credit at nanopub.net's incentive (B1 F6); 'millions' at Giachelle et al.'s abstract ('millions of nanopublications currently available on the Web, especially in the life science domain', B5 F20) and Schultes et al. (B6 F36), the figure the registry calls unchecked (CAP-1-03); nanopub-py (B2 F12) and the site. Force raised: 'three mandatory parts' (T1-2) where nanopub.net says 'three basic elements' (F7) and Giachelle et al. count four with a head (F26); 'heavily concentrated' (T1-8) where the cards say 'especially' and 'chiefly' (F20, F21). Substituted reading: T1-4 puts 'primary source or paper' into the provenance, where Giachelle et al. put 'the evidence paper from which the assertion was extracted' into the publication info (F27) and nanopub.net's provenance names methods and 'the kind of study' (F8); T1-3 narrows the assertion to 'a single, atomic scientific statement or claim', where nanopub.net says it 'can be about anything, for example a relation between a gene and a disease or an opinion' (F3) and Schultes et al. include 'hypotheses, claims, negative results, and opinions' (F35); T1-1's 'rather than a traditional research paper' sets against the article what nanopub.net allows 'with or without an accompanying research article' (F5). Limit dropped: T1-7's 'Citable and Attributed … giving researchers credit' composes the incentive (F6, F16) without its card's limit, 'hard to find and rarely cited' (B5 F22), or the 2021 limit on search and readability (F29); T1-6 composes machine-readability without Schultes et al.'s bound to 'the assertional data type' and small size (B6 F38). Outside the cards' text: 'genetics, pharmacology, and bioinformatics' (T1-8) is in no saved card text or snippet (the cards say 'life science domain'); 'granular data' (T1-7) is in no field claim. Available, not composed: the FAIR headline (F1), the Agent Skill (F11), the Research Object page's own notice of retirement (F13; CAP-1-05), the uptake and 'growing resource of provenance' of the IEEE card (F18), the four parts (F26), the founding motive and the origin in 2009 with Groth et al. and Mons and Velterop (F28, F31; CAP-1-09: 'Groth et al. 2010 appears only in a card'), the Server Network (F34), FANTOM5 (F36), the FAIR Digital Object comparison and its finding (F37, F39, F40), provenance as tracing findings to their origin (F43), Knowledge Pixels and its founders (F45, F49), the publishers' workflows (F48), the machine-reader claims (F46), NanoWeb (F30), retraction (F53), the Medium essay's question (F54). Not surfaced by T and in L_F(B) by the operator's ruling: the architecture page (B10: the second-generation Registry and Query, the legacy server for old unsigned nanopublications, Nanodash, signing over nanopub-http; CAP-1-04) and the encyclopedia's redirect (B11, B12). Composed without attribution: no person, institution or identifier is named in the answer (CAP-1-09, PER 0.75), at the coarse grain of a definition common to its cards except the definition, which is at its sources' grain and carries two markers; in a basin no rival contests. Content replaced by use: the closer (T1-10), an offer menu (N_ext).", "T_vs_LB_reading": "v0.9 §0.5: the first diff is ontological and small. T and the field agree on the entity, an assertion published with its provenance and publication info as one RDF graph; T composes it as a tool for credit and machine reading and leaves out what its own cards give as its limits (rarely cited, hard to find, assertional data only, a retired page among them), its history (2009, FANTOM5) and its people, and it moves the evidence paper from the publication info into the provenance.", "LB_vs_LBA": "Admission adds, in one claim space with the field's: the census record's fields, which restate the own pages and add what the pages do not state, that the model expresses and records provenance and its survival is 'not tested' (PE-04, PE-09), that it is 'NOT a test of whether provenance survives reuse' and that 'publication and signing do not settle an assertion's truth' (PE-13, PE-14), under the census's question 'with what evidence of survival?' (PE-18), with its operator 'the nanopublication community' (PE-15) beside the field's Knowledge Pixels (F45, F49) and its own unchecked items (PE-16); #176's reading of the paradigm as data architecture on the assumption that reception is a parsing problem, with the compositional properties no schema captures, 'proximity of provenance to claims' among them, and its gap claim with its challenge condition (D176-01, D176-03–D176-06, D176-10); nanopublications as the technical infrastructure for training-layer literature's claim-level decomposition and the proposed pilot measuring provenance preservation under retrieval (D176-07–D176-09, D176-11, D176-12); the Claim Status Packet's adoption of nanopublication practice as its closest analogue, and its question of standing (D1529-01–D1529-03); FAIR as the specification of semantic persistence and machine-readable provenance as verifiable by the summarizer (#510, O510-01, O510-02), held apart from #176; the reception consequences metadata standards do not address (#833, O833-01); and the Capture Registry's account of the composition at the name (CAP-1-01–CAP-1-09). No archive claim contradicts a field claim; two qualify one: #176's data-architecture reading qualifies the field's machine-actionability claims (F44, F47, F51, F65), and the census's negative tags qualify the field's citation incentive (F6, F16). Convergences: CAP-1-03 with PE-16 (no count in the record; 'record counts in the Registry' unchecked) against the field's millions (F20, F21, F36); D176-02 (micropublications extend the model) with F38 (the model's scope limited to assertions).", "alignment": { "T1_cards_claims": [ "F1", "F2", "F3", "F4", "F5", "F6", "F7", "F8", "F9", "F10", "F11", "F12", "F13", "F14", "F15", "F16", "F17", "F18", "F19", "F20", "F21", "F22", "F23", "F24", "F25", "F26", "F27", "F28", "F29", "F30", "F31", "F32", "F33", "F34", "F35", "F36", "F37", "F38", "F39", "F40", "F41", "F42", "F43", "F44", "F45", "F46", "F47", "F48", "F49", "F50", "F51", "F52", "F53", "F54", "F65" ], "T1_composed": [ "F2", "F3", "F6", "F7", "F8", "F9", "F10", "F12", "F15", "F16", "F20", "F24", "F33", "F41", "F42", "F47", "F50", "F65" ], "T1_composed_count": "18 of 55 card claims", "T1_outside_cards": [ "'genetics, pharmacology, and bioinformatics' (T1-8): in no card text or snippet", "'mandatory' (T1-2): force raised over F7", "'granular data' (T1-7): in no field claim" ], "T1_substituted": [ "T1-4 (the evidence paper moved into provenance; F27, F8)", "T1-3 (the assertion narrowed to a scientific claim; F3, F35)", "T1-1 ('rather than' for 'with or without'; F5)" ], "rule": "a field claim counts as composed when T states it at its source's grain or coarser; the typology of what is not is in T_vs_LB (§6.2)" } }, "kernel": [ { "K": "K1", "claim": "`PE-01`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "what it is: an assertion published on its own", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K2", "claim": "`PE-02`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "what it is: an assertion published on its own", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the field states the same, one lineage)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K3", "claim": "`PE-03`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "who: Knowledge Pixels and the publishers", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K4", "claim": "`PE-04`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "survival: carried, not tested", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K5", "claim": "`PE-05`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "the structure: assertion, provenance, publication info", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the field states the same, one lineage)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K6", "claim": "`PE-06`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "the structure: assertion, provenance, publication info", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the field states the same, one lineage)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K7", "claim": "`PE-07`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "the carrier: RDF, formal and machine-interpretable", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the field states the same, one lineage)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K8", "claim": "`PE-08`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "what it is: an assertion published on its own", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K9", "claim": "`PE-09`", "source": "provenance census record, 2026-10-29", "M_src": "documented", "sense": "survival: carried, not tested", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K10", "claim": "`PE-10`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "lifecycle: the second generation and the legacy server", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the field states the same, one lineage)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K11", "claim": "`PE-11`", "source": "provenance census record, 2026-10-29", "M_src": "documented", "sense": "lifecycle: the second generation and the legacy server", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the field states the same, one lineage)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K12", "claim": "`PE-12`", "source": "provenance census record, 2026-10-29", "M_src": "documented", "sense": "lifecycle: the second generation and the legacy server", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the field states the same, one lineage)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K13", "claim": "`PE-13`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "survival: carried, not tested", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on survival)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K14", "claim": "`PE-14`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "attribution and citation: the incentive and its limit", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F6, F16: attribution and citation as incentive)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K15", "claim": "`PE-15`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "who: Knowledge Pixels and the publishers", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F45, F49: Knowledge Pixels named by Pensoft)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K16", "claim": "`PE-16`", "source": "provenance census record, 2026-10-29", "M_src": "self-description", "sense": "scale and uptake", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F20, F21, F36: the counts)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K17", "claim": "`PE-17`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "FAIR: containers for FAIR operations", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K18", "claim": "`PE-18`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "survival: carried, not tested", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K19", "claim": "`CAP-1-01`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "the structure: assertion, provenance, publication info", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K20", "claim": "`CAP-1-02`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "reception: the retired page and the encyclopedia", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K21", "claim": "`CAP-1-03`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "scale and uptake", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F20, F21, F36)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K22", "claim": "`CAP-1-04`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "lifecycle: the second generation and the legacy server", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K23", "claim": "`CAP-1-05`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "reception: the retired page and the encyclopedia", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K24", "claim": "`CAP-1-06`", "source": "Capture Registry, 2026-10-29", "M_src": "interpretation", "sense": "the smallest unit of publishable information", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K25", "claim": "`CAP-1-07`", "source": "Capture Registry, 2026-10-29", "M_src": "interpretation", "sense": "survival: carried, not tested", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K26", "claim": "`CAP-1-08`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "reception: the retired page and the encyclopedia", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K27", "claim": "`CAP-1-09`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "origin: 2009–2010", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K28", "claim": "`D176-01`", "source": "#176", "M_src": "interpretation", "sense": "the structure: assertion, provenance, publication info", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K29", "claim": "`D176-02`", "source": "#176", "M_src": "attributed", "sense": "stated limits", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F38: the scope limited to assertions)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K30", "claim": "`D176-03`", "source": "#176", "M_src": "interpretation", "sense": "what it is: an assertion published on its own", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K31", "claim": "`D176-04`", "source": "#176", "M_src": "interpretation", "sense": "machines as readers", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F44, F47, F51, F65: machine-actionability and machine reading as the model's function)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K32", "claim": "`D176-05`", "source": "#176", "M_src": "interpretation", "sense": "machines as readers", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F44, F47)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K33", "claim": "`D176-06`", "source": "#176", "M_src": "interpretation", "sense": "machines as readers", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F23: the repository as a knowledge graph)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K34", "claim": "`D176-07`", "source": "#176", "M_src": "interpretation", "sense": "the archive beside it: training-layer literature and the Claim Status Packet", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K35", "claim": "`D176-08`", "source": "#176", "M_src": "stipulation", "sense": "survival: carried, not tested", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K36", "claim": "`D176-09`", "source": "#176", "M_src": "hypothesis", "sense": "survival: carried, not tested", "qualifiers carried": "—", "f (source's own falsifiers)": "the pilot itself, not run: its metrics name the observation type (provenance preservation under retrieval, D176-08); no threshold stated (watch condition)", "contrast": "missing distinction", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K37", "claim": "`D176-10`", "source": "#176", "M_src": "interpretation", "sense": "machines as readers", "qualifiers carried": "—", "f (source's own falsifiers)": "D176-10 (its own challenge condition: an existing initiative shown to incorporate explicit compositional theory comparable to training-layer literature's; the gap claim revised to relative novelty)", "contrast": "qualified claim (F44, F47, F51)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K38", "claim": "`D176-11`", "source": "#176", "M_src": "stipulation", "sense": "provenance: how the assertion came to be", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K39", "claim": "`D176-12`", "source": "#176", "M_src": "interpretation", "sense": "FAIR: containers for FAIR operations", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F51: an effective FAIR means)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K40", "claim": "`D1529-01`", "source": "#1529", "M_src": "interpretation", "sense": "the archive beside it: training-layer literature and the Claim Status Packet", "qualifiers carried": "D1529-03", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K41", "claim": "`D1529-02`", "source": "#1529", "M_src": "interpretation", "sense": "the archive beside it: training-layer literature and the Claim Status Packet", "qualifiers carried": "D1529-03", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field asks no question of standing)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K42", "claim": "`D1529-03`", "source": "#1529", "M_src": "self-description", "sense": "the archive beside it: training-layer literature and the Claim Status Packet", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K43", "claim": "`O510-01`", "source": "#510", "M_src": "interpretation", "sense": "FAIR: containers for FAIR operations", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F1, F51)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K44", "claim": "`O510-02`", "source": "#510", "M_src": "interpretation", "sense": "machines as readers", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F47) and rival within the archive (D176-04)", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K45", "claim": "`O833-01`", "source": "#833", "M_src": "interpretation", "sense": "survival: carried, not tested", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction", "resolver": "a later capture at 'Nanopublications' (ADDR-94b0d9342da0) on Google AI Overview, seated in the Capture Registry (§8.3)" } ], "kernel_T": [ { "claim": "F22", "note": "the limit 'hard to find and rarely cited', absent" }, { "claim": "F29", "note": "the 2021 limit on search and human-readable counterparts, absent" }, { "claim": "F38", "note": "the scope limited to assertional data and small size, absent" }, { "claim": "F13", "note": "the Research Object page's notice of its own retirement, absent" }, { "claim": "F5", "note": "'with or without an accompanying research article', replaced by 'rather than'" }, { "claim": "F3", "note": "'about anything … or an opinion', narrowed" }, { "claim": "F35", "note": "hypotheses, negative results and opinions, absent" }, { "claim": "F27", "note": "the evidence paper in the publication info, moved to provenance" }, { "claim": "F26", "note": "the four parts with a head, absent" }, { "claim": "F31", "note": "the origin in 2009, absent" }, { "claim": "F28", "note": "the founding motive (attribution, quality and provenance), absent" }, { "claim": "F36", "note": "FANTOM5 (2014), absent" }, { "claim": "F40", "note": "the FAIR Digital Object congruence, absent" }, { "claim": "F45", "note": "Knowledge Pixels and its founders, absent" }, { "claim": "F46", "note": "AI tools that can only guess at narrative results, absent" }, { "claim": "F18", "note": "the IEEE card's 'considerable uptake' and 'growing resource of provenance', absent" } ], "ledger": { "archive": "datasets/negative-of-the-negative/v2/ledgers/nanopublications/ledger-archive.json", "field": "datasets/negative-of-the-negative/v2/ledgers/nanopublications/field.json", "selection": "datasets/negative-of-the-negative/v2/traversal/nanopublications/", "config": "datasets/negative-of-the-negative/v2/panel/configs/nanopublications.json", "intake": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/", "audit": null }, "ontology": { "composition": "equal", "composition_note": "equal-terms case (v0.9 §0.9, §4.1): one claim space; the field's and the archive's claims ordered together by the entity's dependency and by genealogy within each sense; nothing translated; #510 against #176 held under P_coh", "case": { "value": "equal", "statement": "The archive reads the field's entity as the entity: the provenance census records the model from nanopub.net's own pages (its fields restate the home page and the architecture page, each with its quote, basis operator), and the two deposits that name nanopublications take the model as the field gives it, 'machine-readable named graphs consisting of assertion, provenance, and publication metadata' (#176), and adopt its practice as 'the closest existing analogue' (#1529). What the archive adds stands on the field's own object: that the model carries provenance and does not test its survival, that publication and signing do not settle truth (census record); that it treats machine-readability as data architecture where reception is sensitive to composition (#176); that training-layer literature and the Claim Status Packet build on it and ask what it does not, of composition and of standing (#176, #1529). No defining paper contests the field's ontology or supplies one the field lacks: ρ = extends, the equal-terms case (§0.9, §1.2a). One reading within the archive is held under P_coh rather than ruled: #510 holds machine-readable provenance verifiable by the summarizer, #176 holds reception not a parsing problem.", "loci": [ { "dep": 176, "locus": "§5, ¶ \"ORKG / Nanopublications / Micropublications\"", "quote": "The Open Research Knowledge Graph and the nanopublication / micropublication paradigms provide the technical infrastructure for the claim-level decomposition that P1 requires. Training-layer literature adds the literary practice — the genre conventions, stylistic register, and compositional strategies — that these infrastructures lack." }, { "dep": 176, "locus": "§2.2, ¶ \"Nanopublications and Micropublications\" s1", "quote": "The nanopublication paradigm (Mons and Velterop, 2009; Kuhn et al., 2013–) decomposes scientific claims into machine-readable named graphs consisting of assertion, provenance, and publication metadata — individual scientific claims made distinctive, identifiable, citable, and reusable." }, { "dep": 1529, "locus": "§3 \"Five Objects\"", "quote": "The decomposition follows nanopublication practice — assertion, provenance of assertion, publication information kept as separate graphs — which is the closest existing analogue and solves the conflation directly." }, { "dep": "PE", "locus": "census.json rows[slug == 'nanopublications'], retention_results", "quote": "not tested: the model carries provenance; it does not measure its survival" }, { "dep": "PE", "locus": "census.json rows[slug == 'nanopublications'], provenance_object (evidence.self_description, basis operator)", "quote": "an assertion: a small knowledge-graph snippet published on its own" } ] }, "E_F": { "type": "C (public entity: a publication model and its service ecosystem)", "definition": "the nanopublication: a small knowledge-graph snippet with metadata treated as an independent (scientific) publication, its three basic elements an assertion, its provenance (how it came to be) and its publication info (who, when, licence), implemented in RDF, identified by Trusty URIs and signed; conceived from 2009 (Groth et al. 2010; Mons and Velterop 2009); published in millions since FANTOM5 (2014), more than ten million by 2018, chiefly in the life sciences; served now by second-generation Registry and Query services, Nanodash and client libraries, a legacy server keeping old unsigned nanopublications; FAIR-aligned and congruent with FAIR Digital Objects; by its cards' own account hard to find and rarely cited (2021) and limited to small assertional data; in the encyclopedia a section of Microattribution", "claims": [ "F2", "F7", "F8", "F9", "F10", "F33", "F59", "F31", "F36", "F20", "F21", "F56", "F57", "F58", "F51", "F40", "F22", "F38", "F61", "F64" ] }, "E_A": { "definition": "the same model, in the provenance census and the archive's deposits: a publication model and service ecosystem whose object of provenance is an assertion, which expresses and records provenance and does not test its survival, is not a test of whether provenance survives reuse, and whose publication and signing do not settle an assertion's truth (census record); a paradigm that treats machine-readability as data architecture, on the assumption that reception is a parsing problem, where reception is sensitive to compositional properties no schema captures (#176); the technical infrastructure for training-layer literature's claim-level decomposition and the closest analogue of the Claim Status Packet, which asks what standing a claim may carry (#176, #1529)", "claims": [ "PE-01", "PE-02", "PE-04", "PE-09", "PE-13", "PE-14", "PE-18", "D176-01", "D176-04", "D176-05", "D176-07", "D1529-01", "D1529-02", "O833-01" ], "defining_papers": [ 176, 1529, 510, 833 ], "defining_records": [ "provenance census record (census.json rows[slug == 'nanopublications'] and organizing_question; rendered aggregators/nanopublications/index.html; editor Lee Sharks, compiled 2026-10-29, schema 1.0)", "Capture Registry nanopublications-aio-20261029 (OBS-8190a80a3187)" ] }, "rho": { "value": "extends", "status": "read from the census record, the capture record and the two deposits that name nanopublications (§1.2a); #1529 names nanopublication practice its closest analogue and #176 the infrastructure its genre builds on", "statement": "the archive reads E_F as the entity and adds senses and limits on the field's own object: survival not tested and truth not settled by publication or signing (PE-04, PE-09, PE-13, PE-14, PE-18); machine-readability as data architecture where reception is compositional (D176-04, D176-05, D176-06, D176-10); the model as infrastructure for training-layer literature and analogue of the Claim Status Packet, with the questions of composition and of standing (D176-07, D1529-01, D1529-02); measurable reception consequences unaddressed by metadata standards (O833-01); and what the composition layer leaves out of it (CAP-1-04, CAP-1-07)", "claims": [ "PE-04", "PE-09", "PE-13", "PE-14", "PE-18", "D176-04", "D176-05", "D176-06", "D176-10", "D176-07", "D1529-01", "D1529-02", "O833-01", "CAP-1-04", "CAP-1-07" ], "guard": "ρ = extends claims an addition and no more: the census's negative tags state what the model does not do (test survival, settle truth), not a defect in what it does; #176's reading is a gap claim with its own challenge condition (D176-10), not a finding that nanopublications fail, and #176 itself calls them the infrastructure its genre requires (D176-07); #1529 adopts the practice; #510's contrary reading of machine-readable provenance is composed beside #176 under P_coh.", "considered": [ { "value": "constructs", "rejected": "no defining paper reads the model as made by its reception" }, { "value": "revises", "rejected": "the entity is not the archive's own; no earlier archive statement of it is narrowed or withdrawn" } ] }, "translation": [ { "lineage": "what it is: an assertion published on its own", "field_claims": [ "F1", "F2", "F3", "F5", "F14", "F17", "F23", "F35", "F42" ], "received": "F1 (B1, home, headline): \"FAIR data containers for scientific results, and more\"; F2 (B1, home, \"What is a Nanopublication?\" s1): \"A nanopublication is a small knowledge graph snippet with metadata that is treated as an independent (scientific) publication.\"; F3 (B1, home, s2): \"This information in a nanopublication can be about anything, for example a relation between a gene and a disease or an opinion.\"; F5 (B1, home, s4): \"With nanopublications, it is possible to disseminate individual data as independent publications with or without an accompanying research article.\"; F14 (B3, body s1): \"Nano publications provides a model and vocabulary for describing a scientific statement - along with the context for that statement - in a machine readable manner.\"; F17 (B3, body, \"From nanopub.org\" s3): \"Nanopublications are a natural response to the explosion of high-quality contextual information that overwhelms the capacity of conventional research articles in scholarly communication.\"; F23 (B5, Introduction ¶2 s4 (the card's snippet)): \"A repository of nanopublications is to be thought of as an open and interconnected knowledge graph seamlessly integrated with the supporting scientific literature.\"; F35 (B6, Abstract ¶2 s6): \"Nanopublications can be used to expose quantitative and qualitative data, as well as hypotheses, claims, negative results, and opinions that are typically unavailable as structured data or go unpublished altogether.\"; F42 (B7, post of 12 September 2023, \"… so, what exactly is a nanopublication?\"): \"Basically, a nanopublication – unlike a research article – is a tiny snippet of a precise and structured scientific finding (e.g. medication X treats disease Y), which exists as a reusable and cite-able pieces of a growing knowledge graph stored on a decentralised server network\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-01, PE-08, PE-02, D176-03", "archive_claims": [ "PE-01", "PE-08", "PE-02", "D176-03" ] }, { "lineage": "the smallest unit of publishable information", "field_claims": [ "F15", "F41", "F50" ], "received": "F15 (B3, body, \"From nanopub.org\"): \"A publication is the smallest unit of publishable information: an assertion about anything that can be uniquely identified and attributed to its author.\"; F41 (B7, post of 17 May 2023, \"What are nanopublications?\"): \"“the smallest unit of publishable information”, as explained by Knowledge Pixel on nanopub.net.\"; F50 (B8, What are nanopublications? ¶1): \"Nanopublications are a formalized and machine-readable way of communicating the smallest possible units of publishable information. This could be, for example, the outcome of a scientific study or a claim made by a particular scientist.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside CAP-1-06", "archive_claims": [ "CAP-1-06" ] }, { "lineage": "the structure: assertion, provenance, publication info", "field_claims": [ "F7", "F8", "F9", "F26", "F27", "F32", "F52" ], "received": "F7 (B1, home, the three elements: Assertion): \"a nanopublication has three basic elements: … Assertion : The assertion is the main content of a nanopublication in the form of an small atomic unit of information\"; F8 (B1, home, the three elements: Provenance): \"Provenance : This part describes how the assertion above came to be. This can include the scientific methods that were used to generate the assertion, for example a reference to the kind of study that was performed and its parameters.\"; F9 (B1, home, the three elements: Publication Info): \"Publication Info : This part contains metadata about the nanopublication as a whole, such as when and by whom it was created and the license terms for its reuse.\"; F26 (B5, Introduction ¶6 (Fig. 1)): \"The nanopublication is composed of four parts: (i) the head that acts as a connector between the other three sub-graphs; (ii) the assertion graph\"; F27 (B5, Introduction ¶6 (Fig. 1) (iii)–(iv)): \"(iii) the provenance graph (orange) containing metadata about the assertion such as the methods used to generate the assertion and its creators; and (iv) the publication info graph (yellow) containing the metadata about the evidence paper from which the assertion was extracted and about the nanopublication itself.\"; F32 (B6, Abstract ¶2 s3): \"A nanopublication consists of an assertion, the provenance of the assertion, and the provenance of the nanopublication (publication info).\"; F52 (B8, Different elements of a nanopublication): \"From nanopub.org documentation (2020/12/02)\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-05, PE-06, D176-01, CAP-1-01", "archive_claims": [ "PE-05", "PE-06", "D176-01", "CAP-1-01" ] }, { "lineage": "the carrier: RDF, formal and machine-interpretable", "field_claims": [ "F4", "F10", "F19", "F24", "F44", "F63", "F65" ], "received": "F4 (B1, home, s3): \"Nanopublications are expressed in a knowledge graph format that is formal and machine-interpretable.\"; F10 (B1, home, after the elements s1–2): \"Nanopublications are implemented in the language RDF and come with an evolving ecosystem of tools and systems. They can be published to a decentralized server network, for example, and then queried, accessed, reused, and linked.\"; F19 (B5, Abstract s1): \"Nanopublications are Resource Description Framework (RDF) graphs encoding scientific facts extracted from the literature and enriched with provenance and attribution information.\"; F24 (B5, Introduction ¶3 s1–2): \"From the technical viewpoint, a nanopublication is a Resource Description Framework (RDF) graph built around an assertion represented as a triple (subject-predicate-object) and usually extracted, manually or automatically, from a scientific publication. The nanopublication enriches the assertion with provenance and publication information.\"; F44 (B7, post of 12 September 2023, ¶4): \"The machine-actionability of nanopublications is a standard due to each assertion comprising a subject, an object and a predicate (type of relation between the subject and the object), complemented by provenance, authorship and publication information.\"; F63 (B12, section \"Nanopublications\" s2–4 (CC BY 4.0 notice: Giachelle, Dosso and Silvello 2021)): \"From the technical viewpoint, a nanopublication is a Resource Description Framework (RDF) graph built around an assertion represented as a triple (subject-predicate-object) and usually extracted, manually or automatically, from a scientific publication. The nanopublication enriches the assertion with provenance and publication information. The RDF representation format enables interoperability and thus the re-use of data, whereas provenance and publication information eases authorship recognition, credit distribution, and citation.\"; F65 (B5, Conclusions ¶2 s2–3): \"Leveraging on the semantic-oriented RDF structure, nanopublications efficiently convey information and concepts. Hence, these features make nanopublications particularly suitable for enabling data search, information extraction, and automatic reasoning over scientific facts.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-07", "archive_claims": [ "PE-07" ] }, { "lineage": "origin: 2009–2010", "field_claims": [ "F28", "F31", "F62" ], "received": "F28 (B5, Conclusions ¶1 s2): \"the “redundancy of statements in multiple fora makes it difficult to identify attribution, quality, and provenance” (Groth, Gibson & Velterop, 2010)\"; F31 (B6, Abstract ¶2 s1–2): \"Beginning in 2009, nanopublications were independently conceived (Groth et al. 2010) as a minimal, uniform container making individual semantic assertions and their associated provenance metadata, machine-actionable. They represent minimal units of structured data as citable entities (Mons and Velterop 2009).\"; F62 (B12, section \"Nanopublications\" s1): \"Barend Mons and Jan Velterop proposed nanopublications for single, attributable and machine-readable assertions in scientific literature.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside CAP-1-09", "archive_claims": [ "CAP-1-09" ] }, { "lineage": "provenance: how the assertion came to be", "field_claims": [ "F43" ], "received": "F43 (B7, post of 12 September 2023, \"First off, why nanopublications?\"): \"By making it easier to trace individual findings back to their origin and/or follow-up updates, nanopublications also help to better understand the provenance of scientific data.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside D176-11", "archive_claims": [ "D176-11" ] }, { "lineage": "identity and integrity: Trusty URIs and signing", "field_claims": [ "F33", "F59" ], "received": "F33 (B6, Abstract ¶2 s4): \"Nanopublications are implemented in and aligned with Semantic Web technologies such as RDF, OWL, and SPARQL (World Wide Web Consortium (W3C) 2015) and can be permanently and uniquely identified using resolvable Trusty URIs (Groth et al. 2021).\"; F59 (B10, Auxiliary Components: nanopub-http): \"nanopub-http ( code ) is a service that provides features of the nanopublication libraries, most importantly for signing and publishing, over HTTP.\"", "receiving_text": "—", "translation": "untranslated: composed as received (no archive claim in the lineage)", "archive_claims": [] }, { "lineage": "the ecosystem: services, tools, AI agents", "field_claims": [ "F11", "F12", "F30", "F34", "F53", "F55", "F58" ], "received": "F11 (B1, home, last paragraph): \"Nanopublications can also be created, published, and queried conversationally with AI coding agents, through the nanopub Agent Skill\"; F12 (B2, card title and snippet (unreachable: proxy policy 403)): \"GitHub - Nanopublication/nanopub-py: Python client for searching, publishing and modifying nanopublications. · GitHub Overview: Python client (nanopub-py) licensed under Apache-2.0 for searching, publishing, modifying, and retracting nanopublications (machine-readable minimal u...\"; F30 (B5, Abstract s6–7): \"we present the NanoWeb application to seamlessly search, access, explore, and re-use the nanopublications publicly available on the Web. For the time being, NanoWeb focuses on the life science domain where the vastest amount of nanopublications are available.\"; F34 (B6, Abstract ¶2 s5): \"The existing Nanopublication Server Network provides vital services orchestrating nanopublications (Kuhn et al. 2021) including identifier resolution, storage, search and access.\"; F53 (B8, table of contents): \"Publishing nanopublications … Retracting a nanopublication … Searching the nanopub server … Fetching nanopublications\"; F55 (B10, Overall Architecture): \"Nanopublications are published in a decentralized ecosystem of services and applications .\"; F58 (B10, Core Components: Nanodash): \"Nanodash ( instance , code ) is a general client and user interface for nanopublications, It allows for user-friendly browsing, querying, and publishing nanopublications, but can also be used as an API and intermediary layer for other services to build upon.\"", "receiving_text": "—", "translation": "untranslated: composed as received (no archive claim in the lineage)", "archive_claims": [] }, { "lineage": "lifecycle: the second generation and the legacy server", "field_claims": [ "F56", "F57", "F60" ], "received": "F56 (B10, Core Components: Nanopub Registry; legacy nanopub-server): \"Nanopub Registry ( instance , code ) is the second-generation kind of service for publishing and retrieving nanopublications in a decentralized fashion. The legacy nanopub-server ( instance , code ) is still used to keep the old (unsigned) nanopublications, but has otherwise no longer a function in the latest generation of the ecosystem.\"; F57 (B10, Core Components: Nanopub Query): \"Nanopub Query ( instance , code ) forms the second-generation of services to query nanopublications. They allow for decentrally querying the published nanopublications via a number of SPARQL endpoints covering different subsets and aspects of nanopublications.\"; F60 (B10, footer): \"Last updated on Oct 28, 2026\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-11, PE-10, PE-12, CAP-1-04", "archive_claims": [ "PE-11", "PE-10", "PE-12", "CAP-1-04" ] }, { "lineage": "who: Knowledge Pixels and the publishers", "field_claims": [ "F45", "F48", "F49" ], "received": "F45 (B7, post of 17 May 2023, ¶3–4): \"Knowledge Pixels: an innovative startup tech company aiming to revolutionise scientific publishing and knowledge sharing by means of nanopublications … said Philipp von Essen and Tobias Kuhn, the two founders of Knowledge Pixels in a press announcement.\"; F48 (B7, post of 12 September 2023, \"Now, what's new?\"): \"authors in Biodiversity Data Journal (BDJ) can make use of three types of nanopublications:\"; F49 (B7, post of 17 May 2023, \"What can you do in RIO?\"): \"The integration between RIO and Nanodash: the environment developed by Knowledge Pixels where users edit and publish their nanopublications is available at any article published in the journal.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-15, PE-03", "archive_claims": [ "PE-15", "PE-03" ] }, { "lineage": "scale and uptake", "field_claims": [ "F18", "F20", "F21", "F36" ], "received": "F18 (B4, card title and snippet (unreachable: HTTP 202, empty, twice)): \"A Growing Resource of Provenance Abstract: Nanopublications are a Linked Data format for scholarly data publishing that has received considerable uptake in the last few years. In contrast to th...\"; F20 (B5, Abstract s2): \"There are millions of nanopublications currently available on the Web, especially in the life science domain.\"; F21 (B5, Introduction ¶2 s5): \"Hence, this model has been embraced by several scientific fields, especially in the Life Science domain, leading to the creation of more than ten million openly available nanopublications (Kuhn et al., 2018).\"; F36 (B6, Abstract ¶2 s7–8): \"The first practical application of nanopublications occurred in 2014, with the publication of millions of nanopublications as part of the FANTOM5 Project … Since then, millions of real-world examples spanning diverse knowledge domains are now available on the nanopublication server network.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-16, CAP-1-03", "archive_claims": [ "PE-16", "CAP-1-03" ] }, { "lineage": "FAIR: containers for FAIR operations", "field_claims": [ "F37", "F39", "F40", "F51" ], "received": "F37 (B6, Abstract ¶4 s1–2): \"These two technologies share the same vision of a data infrastructure, and act as instances of Machine-Actionable Containers (MACs) that make use of minimal uniform standards to enable FAIR operations.\"; F39 (B6, Abstract ¶5 s4): \"whereas nanopublications represent a moderately mature technology, the FDOF is a specification still under development.\"; F40 (B6, Abstract ¶6 s2): \"We find a remarkable congruence between the currently proposed FDO requirements and the existing nanopublication infrastructure, including several FDO-like qualities already embodied in the nanopublication ecosystem.\"; F51 (B8, What are nanopublications? ¶2): \"Nanopublications are searchable, citable, and contain authorship and attribution information. The aim is to encourage individual scientific results to be released in a traceable and interoperable format. As such, nanopublications are an effective FAIR means of communicating scientific claims and results.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside O510-01, D176-12, PE-17", "archive_claims": [ "O510-01", "D176-12", "PE-17" ] }, { "lineage": "attribution and citation: the incentive and its limit", "field_claims": [ "F6", "F16", "F22", "F25" ], "received": "F6 (B1, home, s5): \"because nanopublications can be attributed and cited, they provide incentives for researchers to make their data available in standard formats that drive data accessibility and interoperability.\"; F16 (B3, body, \"From nanopub.org\" s2): \"Individual nanopublications can be cited by others and tracked for their impact on the community.\"; F22 (B5, Abstract s4–5): \"Nevertheless, they are still not widely used by scientists outside specific circles; they are hard to find and rarely cited. We believe this is due to the lack of services to seek, find and understand nanopublications’ content.\"; F25 (B5, Introduction ¶3 s3): \"The RDF representation format enables interoperability and thus the re-use of data, whereas provenance and publication information eases authorship recognition, credit distribution, and citation.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-14", "archive_claims": [ "PE-14" ] }, { "lineage": "stated limits", "field_claims": [ "F29", "F38" ], "received": "F29 (B5, Conclusions ¶3): \"The central limit to the full exploitation of nanopublications is the lack of services enabling their search, access, exploration, and re-use. Search is limited to the use of structured query languages as SPARQL, and a service to search over all the publicly available nanopublications at once is not available. Nanopublications are machine-readable, but no human-readable counterpart is generated and open to the public.\"; F38 (B6, Abstract ¶5 s2–3): \"The scope of nanopublications is limited to the assertional data type and, as the name suggests, nanopublications should remain small in size (limited to single assertions as individual triples or small RDF graphs). In contrast FDOs are unlimited in their scope\"", "receiving_text": "—", "translation": "untranslated: composed as received beside D176-02", "archive_claims": [ "D176-02" ] }, { "lineage": "machines as readers", "field_claims": [ "F46", "F47", "F54" ], "received": "F46 (B7, post of 17 May 2023, ¶4 (von Essen and Kuhn, quoted)): \"Even the latest impressive AI tools like ChatGPT can only guess (and sometimes ‘hallucinate’) what the authors meant exactly and how the results compare,\"; F47 (B7, post of 17 May 2023, \"Add a nanopublication while writing your manuscript\" ¶3): \"authors ensure that AI assistants, for example, will be more likely to correctly ‘read’, ‘interpret’ and deliver the knowledge reported in the publication for the next users and their prompts.\"; F54 (B9, card title and snippet (unreachable: Cloudflare 403, twice)): \"What is a Nanopublication, really? | by Rohitha Ravinder - Medium In today's AI landscape, this question has become even more important. As systems increasingly generate, summarize and reinterpret scientific knowledge, we find...\"", "receiving_text": "—", "translation": "untranslated: composed as received beside O510-02, D176-04, D176-05, D176-06, D176-10", "archive_claims": [ "O510-02", "D176-04", "D176-05", "D176-06", "D176-10" ] }, { "lineage": "reception: the retired page and the encyclopedia", "field_claims": [ "F13", "F61", "F64" ], "received": "F13 (B3, notice): \"2025-10-13: The RO-Crate website and specification superseded this website after 2020. These pages are no longer maintained.\"; F61 (B11, raw wikitext of \"Nanopublication\" (HTTP 200); \"Nanopublications\" HTTP 404): \"#REDIRECT [[Microattribution]]\"; F64 (B12, rendered article: title, footer and categories): \"Microattribution … (Redirected from Nanopublication) … This legal term article is a stub.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside CAP-1-05, CAP-1-08, CAP-1-02", "archive_claims": [ "CAP-1-05", "CAP-1-08", "CAP-1-02" ] } ], "receiving_texts": "equal-terms case: every field claim composed as received, beside the archive claims it stands with" }, "measure": { "rule": "v0.9 §4.10: KO_B sentences surviving in the KO at similarity ≥ 0.95, with positions (computed as apply_v09.py does: difflib.SequenceMatcher ratio, the best KO sentence for each KO_B sentence)", "v0.9": { "surviving": 0, "of": 13, "positions": [ null, null, null, null, null, null, null, null, null, null, null, null, null ] }, "opening_run": { "rule": "v0.9 §5.10 (equal-terms case): the field-only KO's sentences as the KO's opening run in their own order", "breach": false }, "blocks": { "rule": "v0.9 §4.1 (equal-terms and mixed cases): the KO does not open with the field as a block or close with the archive as one; sentences typed by the ledgers of the claims they cite (F field-only, A archive-only, M both)", "sequence": "MFMMFMMFMFFMFMFMMMFFMAMMAAAMA", "field_only_head": 0, "archive_only_tail": 1, "breach": false }, "max_similarity": [ 0.12, 0.091, 0.223, 0.13, 0.076, 0.134, 0.096, 0.147, 0.173, 0.17, 0.206, 0.295, 0.444 ], "ko_sentence_1_max_similarity_to_KO_B": 0.242 }, "homonyms": { "names": [], "basis": "The census row carries no disambiguation field; no card is a homonym and T has no homonym panel. 'Nanopublication' (the GitHub organisation on card 2) names the community's code, not another entity. The encyclopedia folds the entity into Microattribution (a distinct concept: data citation credit), which is recorded as the encyclopedia's placement, not as a sense of the name.", "distinct_entities": [ "Microattribution (the encyclopedia article the title redirects into; Axton 2007)", "micropublications (Clark et al. 2014; D176-02, an extension of the model)", "FAIR Digital Objects (the framework B6 compares)", "RO-Crate and the Research Object model (B3, the retired page's successor specification)", "Knowledge Pixels (the company B7 names; F45, F49)", "NanoWeb (B5's application)", "the Claim Status Packet (#1529) and training-layer literature (#176), archive objects built on the model", "ProvStore (the census's neighbour for this entity; its /non row datasets/negative-of-the-negative/v2/rows/provstore.json)" ], "neighbours": [ { "entity": "provstore", "relation": "the census's neighbour (relations[0]); census record https://www.provenanceerasure.org/aggregators/provstore/", "row": "datasets/negative-of-the-negative/v2/rows/provstore.json (built the same day; not edited)" }, { "entity": "data-provenance-explorer", "relation": "a provenance resource of the training layer (MMRS row); not a census neighbour of this entity", "row": "datasets/negative-of-the-negative/v2/rows/data-provenance-explorer.json" } ], "substitutes": { "T": [] }, "register": { "address_1": { "slug": "nanopublications-aio-20261029", "obs_id": "OBS-8190a80a3187" } } }, "notes": [ "One address, Google AI Overview (expanded), signed out, incognito, 2026-10-29: nanopublications-aio-20261029 (OBS-8190a80a3187, ADDR-94b0d9342da0, AXN:0AD2.CAPTURE.🎇🖐️🍂📌🍂🌲), nine cards, 202 words in the answer body. A NEW address; the census record landed the same day and no card cites it (CAP-1-08).", "Wikipedia: no article. 'Nanopublication' is a redirect to Microattribution with no section named (raw wikitext '#REDIRECT [[Microattribution]]', HTTP 200); the rendered page is the Microattribution article, a legal-term stub (categories Copyright law, Academic publishing), whose section 'Nanopublications' is ledgered (F62–F64): one sentence crediting Mons and Velterop and two reproduced from Giachelle, Dosso and Silvello 2021 (card B5) under a CC BY 4.0 notice. 'Nanopublications' (plural) returns HTTP 404. Two earlier requests (17:07 and 17:09 UTC) answered HTTP 429.", "Fetching: card pages saved verbatim with curl on 2026-10-29 between 17:07 and 17:17 UTC, raw and text with sha256 in field.json; B1 (the home page, also a card) and B10 (the architecture page) are the census's saved copies (sha256 matching the census record), not refetched. Card URLs were found by WebSearch on title and site (B3, B5, B6, B8, B9), by the card's title read as a path (B2), by the article number from the VU Amsterdam portal (B4), and by the tag page's title and the snippet's text (B7). B6's text adds the article frame the page loads. B5 answered a reCAPTCHA interstitial on the first request and the article on a plain retry; a second request with browser headers was refused by the session's permission classifier as bot-check circumvention and was not pursued.", "Unreachable (card title and snippet stand as their only text): B2 GitHub (the session's egress proxy: HTTP 403, a policy denial, not retried); B4 IEEE Xplore (HTTP 202, empty body, twice; the arXiv preprint of the same paper was not admitted as the card's text); B9 Medium (Cloudflare HTTP 403, twice).", "The archive subset: the string pass returned 7 D, 0 R and 16 O candidates in 9 deposits; a grep of every deposit text for 'nanopub' returns only #176 and #1529. Reading admitted 4 deposits (#176 D/R/O, #1529 D/R, #510 O, #833 O; #510 and #833 borderline, admitted for the tail with reasons) with 18 claims, and rejected 5 (#1, #106, #868, #875, #876). The hop (93 candidates in 92 deposits) admitted none; it was screened by alias, class and provenance-vocabulary strings and the hits read, not read whole. Two passages were admitted by reading as continuations of their candidates (#176 ¶49 and ¶128; #510 Step 2). The census record (18 claims, PE-01–PE-18) and the Capture Registry entry (9 claims, CAP-1-01–CAP-1-09) are ledgered beside the deposits.", "Defects and disagreements in the census record, reported, not fixed: (1) operator 'the nanopublication community (nanopub.net)' has no evidence quote, and neither saved own page names an operator; Pensoft (card B7) names Knowledge Pixels, founded by Philipp von Essen and Tobias Kuhn, as the explainer on nanopub.net and the developer of Nanodash (one of the record's own aka). (2) provenance_carrier gives three parts; card B5 (Giachelle, Dosso and Silvello 2021) describes four, a head graph joining the three; not a contradiction of the own page ('three basic elements'), recorded as an open question. (3) The record names signing only through 'old unsigned nanopublications'; the architecture page it saved names nanopub-http 'most importantly for signing and publishing' (F59), which no field of the record carries. (4) 'record counts in the Registry' is unchecked; the cards give counts (millions, B5 abstract; more than ten million by 2018, B5 citing Kuhn et al.; FANTOM5 millions, B6). No field of the record is contradicted by a fetched source or shown out of date by the capture.", "On the capture record, reported, not fixed: finding 2 ('MILLIONS' … 'the figure comes through the composition from the cards and is unchecked') stands as the registry's statement; the field locates the figure at card B5's abstract ('There are millions of nanopublications currently available on the Web, especially in the life science domain') and B6, so it is at a card's grain, and T's disciplines ('genetics, pharmacology, and bioinformatics') are not. Finding 3 says the record 'carries' signing from the architecture page; the record carries the Registry, Query and the legacy server, and signing only by implication (see the census note (3)). The analysis ('composed from its own definition at full grain') holds for the three parts; T's opening definition joins nanopub.net's current definition with the older nanopub.org phrase quoted on two other cards (B3, B7).", "Composition: the KO and the compression were composed from the ledgers; the transcript was read only for T's claims and the delta, as the brief asks. KO 29 sentences, every field claim (65) and every archive claim (45) cited; P body 315 words, open block outside the bound; KO_B 13 sentences, none surviving at ≥ 0.95 (KO sentence 1's best similarity to a KO_B sentence 0.242). The ledgers are unaudited (one extractor each).", "Related rows: ProvStore, the census's neighbour (relations[0]), has its /non row at datasets/negative-of-the-negative/v2/rows/provstore.json (built the same day); not edited. The Data Provenance Explorer row (datasets/negative-of-the-negative/v2/rows/data-provenance-explorer.json) is the MMRS row on training-data provenance; not edited.", "earliest dated instance: B4 2018 (IEEE eScience), B8 2020-12-02 (its copy of nanopub.org), B5 2021-02, B6 2022-10-12, B7 2023, B3 notice 2025-10-13, B10 2026-10-28; #176 2026-06-09, #833 2026-06-15, #1529 2026-08-21; B1, B2, B9 undated" ], "composition_v09": { "source": "this row (composed directly; no rebuild/negative-of-the-negative/v09/nanopublications.json)", "composer": "Claude (Opus 5.5), subagent, 2026-10-29", "defining_material_read": [ { "what": "provenance census record, row", "file": "/home/claude/fleet/provenance-erasure/data/provenance-census/census.json (rows[slug == 'nanopublications'], schema_note, organizing_question)", "read": "whole" }, { "what": "provenance census record, rendered", "file": "/home/claude/fleet/provenance-erasure/aggregators/nanopublications/index.html", "read": "text, for agreement with the census row" }, { "what": "the census's saved sources", "file": "/home/claude/fleet/provenance-erasure/data/provenance-census/sources/nanopublications--home.* and nanopublications--architecture.* (and manifest.json)", "read": "whole" }, { "what": "capture record", "file": "data/EA-WG-CAPTURES-01.json (nanopublications-aio-20261029)", "read": "transcript, transcript_raw, cite_list, d, reading, findings, analysis, q_kind, per_note, originator" }, { "dep": 176, "file": "data/texts/AXN-0313-text.md", "read": "§1–§2.3, §4 P4, §5, §6 (metrics and pilot) and Appendix B, around every passage naming nanopublications" }, { "dep": 1529, "file": "data/texts/AXN-062E-text.md", "read": "status, §0 opening, §2, §3" }, { "dep": 510, "file": "data/texts/AXN-014D-text.md", "read": "the passage of Steps 1–3" }, { "dep": 833, "file": "data/texts/AXN-034E-text.md", "read": "§9 close and §10" }, { "what": "the specification", "file": "data/texts/AXN-0700-text.md", "read": "§0–§11 whole; Appendix A" }, { "what": "exemplars", "file": "rows/google-ai-overviews.json, rows/ai-overview-capture-registry.json (structure), rows/data-provenance-explorer.json (shape mirrored), rebuild/negative-of-the-negative/v09/BRIEF.md, apply_v09.py", "read": "structure and the Compose section" } ], "cuts": [], "notes": "equal case; KO 29 sentences, all 65 field and 45 archive claims cited; P body 315 words; KO_B 13 sentences, none surviving at ≥ 0.95" }, "field_by_origin": { "cards": [ "B1", "B2", "B3", "B4", "B5", "B6", "B7", "B8", "B9" ], "own_pages": [ "B10" ], "wikipedia": [ "B11", "B12" ], "census_third_party": [], "census_third_party_note": "none: every evidence entry of the census record has basis 'operator'", "unreachable": [ "B2", "B4", "B9" ], "title_only": [ "B2", "B4", "B9" ], "own_page_also_card": [ "B1" ], "wikipedia_state": "no article: 'Nanopublication' is a redirect ('#REDIRECT [[Microattribution]]', raw wikitext HTTP 200), no section named; the rendered page is Microattribution '(Redirected from Nanopublication)', a legal-term stub (categories Copyright law, Academic publishing) with a section headed 'Nanopublications' of three sentences, two of them reproduced from Giachelle, Dosso and Silvello (2021) under a CC BY 4.0 notice; 'Nanopublications' (plural) has no page (raw wikitext HTTP 404). Two earlier requests answered HTTP 429 (2026-10-29)", "sources": [ { "id": "B1", "origin": "card", "role": "Overview card 1; also the own page the census record cites (census source nanopublications--home)", "card": "Nanopublications — Nanopublications", "url": "https://nanopub.net/", "kind": "Overview card (own page)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 1 } ], "files": { "B1.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B1.html", "sha256": "b2d9af40755a66ed0efd1b37d10933140d8c0860425721d41075dbc2679cbf5d" }, "B1.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B1.txt", "sha256": "8be928dfb8148a200397c972986fc2083de55c1a98bde41849e901f1115554d4" } }, "fetched": { "by": "the provenance census (copy of its saved source, not refetched)", "census_source": "nanopublications--home", "url": "https://nanopub.net/", "read": "2026-10-29", "at": "2026-10-29T15:55:22Z (census manifest)", "http": 200, "raw": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B1.html", "raw_sha256": "b2d9af40755a66ed0efd1b37d10933140d8c0860425721d41075dbc2679cbf5d", "census_sha256": "b2d9af40755a66ed0efd1b37d10933140d8c0860425721d41075dbc2679cbf5d", "sha256_match": true, "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B1.txt" ], "text_from": "the census text file nanopublications--home.txt, copied verbatim" }, "names_operator": "no (names nanopub.net only as the site; no organisation or person)", "names_archive": "no", "note": "the card is the home page the census record cites; carried once, as a card (origin card), with the census copy (sha256 matches the census record)" }, { "id": "B2", "origin": "card", "role": "Overview card 2", "card": "GitHub — GitHub - Nanopublication/nanopub-py: Python client for searching, publishing and modifying nanopublications. · GitHub", "url": "https://github.com/Nanopublication/nanopub-py", "kind": "Overview card (code repository)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 2 } ], "files": { "B2.response.json": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B2.response.json", "sha256": "b3e03aaaff81d68730d67392a135ac3fdfdf022880c66632ab188d2fe084cda3" } }, "fetched": { "unreachable": true, "attempts": [ { "at": "2026-10-29T17:06:5xZ", "http": 403, "by": "the session's egress proxy, a policy denial ('GitHub access to this repository is not enabled for this session'), body saved as B2.response.json" } ], "retries": "none: the proxy instructs that policy denials are not retried", "url_found_by": "the card title (owner/repository) read as the GitHub path", "text": "card title and snippet only (cite_list n=2)" }, "names_operator": "no (the snippet names the repository owner \"Nanopublication\")", "names_archive": "no", "note": "unreachable; its title and snippet stand as its only text" }, { "id": "B3", "origin": "card", "role": "Overview card 3", "card": "researchobject.org — Nanopublications - Research Object", "url": "https://www.researchobject.org/initiative/nanopublications/", "kind": "Overview card (third-party page, retired)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 3 } ], "files": { "B3.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B3.html", "sha256": "256a144820942c0809563173dd798042da59fcf41e3199331132a0f847c3ee50" }, "B3.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B3.txt", "sha256": "e171654d688c2ab07efea844300fe00509fd9d2dd3d59d77244f52323057463b" } }, "fetched": { "at": "2026-10-29T17:07:29Z", "http": 200, "url": "https://www.researchobject.org/initiative/nanopublications/", "raw": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B3.html", "raw_sha256": "256a144820942c0809563173dd798042da59fcf41e3199331132a0f847c3ee50", "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B3.txt" ], "url_found_by": "WebSearch on the title and site" }, "names_operator": "no (quotes \"nanopub.org\" as its source)", "names_archive": "no", "note": "the page carries its own notice that it is superseded and no longer maintained (F13)" }, { "id": "B4", "origin": "card", "role": "Overview card 4", "card": "IEEE Xplore — A Growing Resource of Provenance", "url": "https://ieeexplore.ieee.org/document/8588643", "kind": "Overview card (paper: Kuhn et al., \"Nanopublications: A Growing Resource of Provenance-Centric Scientific Linked Data\", IEEE eScience 2018, doi:10.1109/eScience.2018.00024)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 4 } ], "files": { "B4.response.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B4.response.html", "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855" }, "B4.response-2.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B4.response-2.html", "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855" } }, "fetched": { "unreachable": true, "attempts": [ { "at": "2026-10-29T17:08:21Z", "http": 202, "bytes": 0 }, { "at": "2026-10-29T17:17:18Z", "http": 202, "bytes": 0 } ], "retries": "one plain retry with the same command; both answered HTTP 202 with an empty body", "url_found_by": "WebSearch on the title (arXiv:1809.06532 preprint and the VU Amsterdam research portal); the portal gives article number 8588643 and doi 10.1109/eScience.2018.00024", "text": "card title and snippet only (cite_list n=4)", "not_used": "the arXiv preprint of the same paper (arxiv.org/abs/1809.06532) is reachable; it is not the card and was not admitted as its text" }, "names_operator": "no", "names_archive": "no", "note": "unreachable; its title and snippet stand as its only text" }, { "id": "B5", "origin": "card", "role": "Overview card 5", "card": "National Institutes of Health (NIH) | (.gov) — Search, access, and explore life science nanopublications on the Web", "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC7959622/", "kind": "Overview card (paper: Giachelle, Dosso and Silvello, PeerJ Computer Science 7: e335, 2021, PMC7959622)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 5 } ], "files": { "B5.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B5.html", "sha256": "8f174f1e4a6e24025943ce70c8ba26b89847a4e8f39526f828c1323604a2127b" }, "B5.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B5.txt", "sha256": "00e13d3c91b77d7deb41537634e8095854076d28aff64b458db3a21981f990db" }, "B5.response.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B5.response.html", "sha256": "935f022b8560df6a0956314d08f495d64815509cb577154be6eeecb234e47fe4" } }, "fetched": { "at": "2026-10-29T17:17:19Z", "http": 200, "url": "https://pmc.ncbi.nlm.nih.gov/articles/PMC7959622/", "raw": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B5.html", "raw_sha256": "8f174f1e4a6e24025943ce70c8ba26b89847a4e8f39526f828c1323604a2127b", "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B5.txt" ], "attempts": [ { "at": "2026-10-29T17:08:22Z", "http": 200, "note": "a 'Checking your browser - reCAPTCHA' interstitial, saved as B5.response.html" }, { "at": "2026-10-29T17:17:19Z", "http": 200, "note": "the article (plain retry with the same command); saved as B5.html" } ], "url_found_by": "WebSearch on the title" }, "names_operator": "no", "names_archive": "no", "note": "the encyclopedia section B12 reproduces three of its sentences under a CC BY 4.0 notice (one lineage, B5 earliest)" }, { "id": "B6", "origin": "card", "role": "Overview card 6", "card": "Research Ideas and Outcomes — The Comparative Anatomy of Nanopublications and FAIR Digital ...", "url": "https://riojournal.com/article/94150/", "kind": "Overview card (conference abstract: Schultes, Magagna, Kuhn, Suchánek, Bonino da Silva Santos and Mons, RIO 8: e94150, 12 Oct 2022)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 6 } ], "files": { "B6.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B6.html", "sha256": "5e1d57ffd1eaf59091c3415ed6ba901c30167751e92a4b1a5d402653e6b287cc" }, "B6-article.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B6-article.html", "sha256": "637e1641f206653fb10042d305251314881ffcd84183b163db5aedbbf60d7c0c" }, "B6.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B6.txt", "sha256": "536e1554173fc6728ededed1cb5b49766210fad55b50e6b002be1d7cfbde0625" } }, "fetched": { "at": "2026-10-29T17:08:25Z", "http": 200, "url": "https://riojournal.com/article/94150/", "raw": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B6.html", "raw_sha256": "5e1d57ffd1eaf59091c3415ed6ba901c30167751e92a4b1a5d402653e6b287cc", "frame": { "at": "2026-10-29T17:09:49Z", "http": 200, "url": "https://riojournal.com/article_preview.php?id=94150", "sha256": "637e1641f206653fb10042d305251314881ffcd84183b163db5aedbbf60d7c0c" }, "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B6.txt" ], "text_from": "the page's text, then (under a marked header) the text of the article frame the page loads (article_preview.php?id=94150, saved B6-article.html)", "url_found_by": "WebSearch on the title" }, "names_operator": "no (its authors include Tobias Kuhn and Barend Mons; no operator of nanopub.net is named)", "names_archive": "no", "note": "" }, { "id": "B7", "origin": "card", "role": "Overview card 7", "card": "Pensoft blog — nanopublications", "url": "https://blog.pensoft.net/tag/nanopublications/", "kind": "Overview card (publisher blog, tag page of three posts: 17 June 2024, 12 September 2023, 17 May 2023)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 7 } ], "files": { "B7.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B7.html", "sha256": "90c7b9d5a5bc8c1d0281ad47ac27ca47829754d6d817b23057b74b0a60940e51" }, "B7.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B7.txt", "sha256": "9bffd0db11eef492261c10534852c24df02cf4056c734174f1f4e0016c80992c" } }, "fetched": { "at": "2026-10-29T17:07:32Z", "http": 200, "url": "https://blog.pensoft.net/tag/nanopublications/", "raw": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B7.html", "raw_sha256": "90c7b9d5a5bc8c1d0281ad47ac27ca47829754d6d817b23057b74b0a60940e51", "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B7.txt" ], "url_found_by": "the card's title ('nanopublications', the tag page's title 'nanopublications | Blog') and its snippet, found verbatim in the tag page" }, "names_operator": "yes: Knowledge Pixels, \"as explained by Knowledge Pixel on nanopub.net\", its founders Philipp von Essen and Tobias Kuhn, the developer of Nanodash (F41, F45, F49)", "names_archive": "no", "note": "" }, { "id": "B8", "origin": "card", "role": "Overview card 8", "card": "Read the Docs — What are nanopublications? — nanopub 1.2.11 documentation", "url": "https://nanopub.readthedocs.io/en/latest/getting-started/what-are-nanopubs.html", "kind": "Overview card (library documentation, nanopub 1.2.11)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 8 } ], "files": { "B8.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B8.html", "sha256": "2b3fc9e3f01b044f55e4929af2b2e7bed32aa4eb7dcca6e66ba19b911a7224f1" }, "B8.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B8.txt", "sha256": "8df48d6cc498c58bfa564ab80cdedad40cd170386b56059b968a27a87a4b014a" } }, "fetched": { "at": "2026-10-29T17:07:31Z", "http": 200, "url": "https://nanopub.readthedocs.io/en/latest/getting-started/what-are-nanopubs.html", "raw": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B8.html", "raw_sha256": "2b3fc9e3f01b044f55e4929af2b2e7bed32aa4eb7dcca6e66ba19b911a7224f1", "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B8.txt" ], "url_found_by": "WebSearch" }, "names_operator": "no (cites nanopub.org documentation, 2020/12/02)", "names_archive": "no", "note": "" }, { "id": "B9", "origin": "card", "role": "Overview card 9", "card": "Medium — What is a Nanopublication, really? | by Rohitha Ravinder - Medium", "url": "https://medium.com/@rohitha0112/what-is-a-nanopublication-really-413cac6da0dd", "kind": "Overview card (essay)", "surfaced_by_T": [ { "slug": "nanopublications-aio-20261029", "card": 9 } ], "files": { "B9.response.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B9.response.html", "sha256": "5d030b7a8de8b19f15f2ca455f1872913aca9ae7f7523f9d5fba6b4c347eefd1" }, "B9.response-2.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B9.response-2.html", "sha256": "663af2e705919c558eb95ae942689ff5bc2968cffb3591f37aa1470a40a181e8" } }, "fetched": { "unreachable": true, "attempts": [ { "at": "2026-10-29T17:09:02Z", "http": 403, "bytes": 5188 }, { "at": "2026-10-29T17:17:19Z", "http": 403, "bytes": 5188 } ], "retries": "one plain retry with the same command; both HTTP 403, Cloudflare 'Attention Required!'", "url_found_by": "WebSearch (extended) on the title", "text": "card title and snippet only (cite_list n=9)" }, "names_operator": "no", "names_archive": "no", "note": "unreachable; its title and snippet stand as its only text" }, { "id": "B10", "origin": "own_page", "role": "the own page the census record cites (census source nanopublications--architecture); not surfaced by T", "card": "Nanopublications — Technical Architecture | Nanopublications", "url": "https://nanopub.net/docs/architecture/", "kind": "own page (documentation)", "surfaced_by_T": "no (not surfaced by T; admitted by the operator's ruling of 2026-10-29 as an own page the census record cites)", "files": { "B10.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B10.html", "sha256": "0e21d7ae559d83011d3897162f9518043240fd9cd5d901086d980577f54e5e3f" }, "B10.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B10.txt", "sha256": "813446192dbaa9d5805a8ec17276982ba3ba75a18959dba11ba1ac68f8f348f2" } }, "fetched": { "by": "the provenance census (copy of its saved source, not refetched)", "census_source": "nanopublications--architecture", "url": "https://nanopub.net/docs/architecture/", "read": "2026-10-29", "at": "2026-10-29T15:55:22Z (census manifest)", "http": 200, "raw": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B10.html", "raw_sha256": "0e21d7ae559d83011d3897162f9518043240fd9cd5d901086d980577f54e5e3f", "census_sha256": "0e21d7ae559d83011d3897162f9518043240fd9cd5d901086d980577f54e5e3f", "sha256_match": true, "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B10.txt" ], "text_from": "the census text file nanopublications--architecture.txt, copied verbatim" }, "names_operator": "no", "names_archive": "no", "note": "page dated by itself \"Last updated on Oct 28, 2026\" (F60)" }, { "id": "B11", "origin": "wikipedia", "role": "the entity's Wikipedia title", "card": "Wikipedia — Nanopublication (redirect to Microattribution)", "url": "https://en.wikipedia.org/wiki/Nanopublication", "kind": "Wikipedia (redirect)", "surfaced_by_T": "no (not surfaced by T; checked by the operator's ruling of 2026-10-29)", "files": { "B11.wiki": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B11.wiki", "sha256": "d41abb95f2384221b3eaf8b8de07aac7f46f8c0027543820c86709fc7716dd1c" }, "B11-plural.wiki": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B11-plural.wiki", "sha256": "7add8a12ea86f08efd87ce607961a6530e8cdd8fda4be8a74221ac3b5f561523" }, "B11.response-1.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B11.response-1.html", "sha256": "e0c2bb17090d654fb895cd622c55770bce9b634c92316f5f4bb8bbd4128ddd32" }, "B11.response-2.wiki": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B11.response-2.wiki", "sha256": "6810f9dd8e60164827c750f5c58ec53550a2fc2667865d99fadd1ffff069b1b0" }, "B11.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B11.txt", "sha256": "b7ba406f1fd53a990cfbefaf00f8ba6e650b62b633120fed782de071a0453b76" } }, "fetched": { "raw": { "at": "2026-10-29T17:16:30Z", "http": 200, "url": "https://en.wikipedia.org/w/index.php?title=Nanopublication&action=raw&redirect=no", "sha256": "d41abb95f2384221b3eaf8b8de07aac7f46f8c0027543820c86709fc7716dd1c" }, "plural_raw": { "at": "2026-10-29T17:16:42Z", "http": 404, "url": "https://en.wikipedia.org/w/index.php?title=Nanopublications&action=raw&redirect=no", "sha256": "7add8a12ea86f08efd87ce607961a6530e8cdd8fda4be8a74221ac3b5f561523" }, "rate_limited_earlier": [ { "file": "B11.response-1.html", "at": "2026-10-29T17:07:35Z", "http": 429 }, { "file": "B11.response-2.wiki", "at": "2026-10-29T17:09:03Z", "http": 429 } ], "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B11.txt" ], "text_from": "a summary of the responses with the whole redirect wikitext quoted" }, "names_operator": "no", "names_archive": "no", "note": "the singular title is a redirect to Microattribution (no section named in the redirect); the plural title has no page (HTTP 404)" }, { "id": "B12", "origin": "wikipedia", "role": "the article the title redirects into, section \"Nanopublications\" ledgered", "card": "Wikipedia — Microattribution, section \"Nanopublications\"", "url": "https://en.wikipedia.org/wiki/Microattribution#Nanopublications", "kind": "Wikipedia (article section; a legal-term stub)", "surfaced_by_T": "no (not surfaced by T; checked by the operator's ruling of 2026-10-29)", "files": { "B12.wiki": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B12.wiki", "sha256": "ff14b0cdc5715120149b37f2710a54ed2adbf9fe0b80191174d8a03cdfafb73e" }, "B12.html": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B12.html", "sha256": "3080a6d305f790d788b65ac3a008f682625c7192a07dd820ca50c134d511b492" }, "B12.txt": { "path": "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B12.txt", "sha256": "24e5e8d89fb2dfac959a524eda759756e65fdbe66ed2d2faf8eedf8711bd6325" } }, "fetched": { "raw": { "at": "2026-10-29T17:16:39Z", "http": 200, "url": "https://en.wikipedia.org/w/index.php?title=Microattribution&action=raw", "sha256": "ff14b0cdc5715120149b37f2710a54ed2adbf9fe0b80191174d8a03cdfafb73e" }, "rendered": { "at": "2026-10-29T17:16:41Z", "http": 200, "url": "https://en.wikipedia.org/wiki/Nanopublication", "sha256": "3080a6d305f790d788b65ac3a008f682625c7192a07dd820ca50c134d511b492" }, "text": [ "datasets/negative-of-the-negative/v2/intake/nanopublications-20261029/B12.txt" ], "text_from": "the rendered page (fetched at the Nanopublication title, \"(Redirected from Nanopublication)\"), scripts and styles stripped" }, "names_operator": "no (names Barend Mons and Jan Velterop as proposers)", "names_archive": "no", "note": "the section reproduces three sentences of B5 under a CC BY 4.0 notice (one lineage with B5, which keeps the earliest date)" } ] } }