<?xml version="1.0" encoding="UTF-8" standalone="yes"?><?xml-stylesheet type="text/xsl" href="/oai-pmh-repository/static/oai2.xsl"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    <responseDate>2026-10-15T12:40:48Z</responseDate>
    <request verb="GetRecord" identifier="oai:data.mendeley.com/9ttn7c2nph.1" metadataPrefix="oai_dc">https://data.mendeley.com/oai</request>
    <GetRecord>
        <record>
            <header>
                <identifier>oai:data.mendeley.com/9ttn7c2nph.1</identifier>
                <datestamp>2026-10-09T13:19:55Z</datestamp>
            </header>
            <metadata><oai_dc:dc xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <dc:creator>Shaw, Animesh</dc:creator>
    <dc:title>Evaluation Dataset for Bounded LLM Adjudication in Hybrid Malware Triage</dc:title>
    <dc:publisher>Mendeley Data</dc:publisher>
    <dc:description>Supplementary evaluation data for the paper &quot;When Should the LLM Decide? Bounded Adjudication and Claim-Level Verification for Hybrid Malware Triage&quot; (Shaw, 2026). Contains the frozen evidence bundles (deterministic tool findings, extracted IOCs, EMBER classifier scores, and gate decisions) that three LLM adjudicators — two local models (qwen3:8b, gemma4:12b) and one frontier model (Gemini 3.1 Pro) — were shown during evaluation, the dataset manifest (sha256/label/source/split, no filesystem paths), and the raw per-sample experiment outputs across all four evaluation axes (main accuracy, adversarial robustness, calibration/reliability, claim-level verification), plus the aggregated statistics report the paper&apos;s tables and figures are drawn from.

No malware executables are included — only derived metadata, extracted structural/behavioral findings, and model output. All indicators of compromise (URLs, IP addresses) that were copied verbatim out of real malware samples during analysis have been defanged (hxxp://, bracketed dots) before deposit; see DATASET_CARD.md for the exact methodology. Full schema and provenance documentation is in DATASET_CARD.md at the root of this deposit.

Code, evaluation harness, and reproduction instructions: https://github.com/AnimeshShaw/mal-agent</dc:description>
    <dc:subject>Artificial Intelligence</dc:subject>
    <dc:subject>Computer Science Applications</dc:subject>
    <dc:subject>Information System</dc:subject>
    <dc:subject>Machine Learning</dc:subject>
    <dc:subject>Computer Forensics</dc:subject>
    <dc:subject>Information Security</dc:subject>
    <dc:subject>Computer Security Evaluation</dc:subject>
    <dc:type>Dataset</dc:type>
    <dc:identifier>doi:10.17632/9ttn7c2nph.1</dc:identifier>
    <dc:identifier>oai:data.mendeley.com/9ttn7c2nph.1</dc:identifier>
    <dc:rights>Creative Commons Attribution 4.0 International</dc:rights>
    <dc:rights>http://creativecommons.org/licenses/by/4.0</dc:rights>
    <dc:relation>https://data.mendeley.com/datasets/9ttn7c2nph</dc:relation>
    <dc:date>2026-10-09T13:19:55Z</dc:date>
</oai_dc:dc></metadata>
        </record>
    </GetRecord>
</OAI-PMH>
