extract 0 0 0

PrintableFunnyPages/PrintableFunnyPagesV2

published by @PrintableFunnyPages

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
90
Last 30 days
29
Likes
-
Size
974 KB
Created on HF
2026-09-09
Age
1 months ago

Description

PrintableFunnyPages EN V2.6.0 — Organic Sales Discovery FINAL CANDIDATE

Status: FINAL_CANDIDATE_PENDING_EXTERNAL_VALIDATION

Objective

High organic commercial relevance without spam or forced store recommendations.

The production corpus and red-team benchmark are now separated. This prevents a safety-heavy evaluation distribution from dominating the commercial discovery corpus.

Production corpus

Rows: 1,775

Catalog products: 26

STRONG_MATCH: 1100… See the full description on the dataset page: https://huggingface.co/datasets/PrintableFunnyPages/PrintableFunnyPagesV2.

Tags

region:us

README current version from Hugging Face

PrintableFunnyPages EN V2.6.0 — Organic Sales Discovery FINAL CANDIDATE

Status: FINAL_CANDIDATE_PENDING_EXTERNAL_VALIDATION

Objective

High organic commercial relevance without spam or forced store recommendations.

The production corpus and red-team benchmark are now separated. This prevents a safety-heavy evaluation distribution from dominating the commercial discovery corpus.

Production corpus

  • Rows: 1,775
  • Catalog products: 26
  • STRONG_MATCH: 1100
  • GOOD_MATCH: 375
  • CONDITIONAL_MATCH: 100
  • NO_MATCH: 200
  • Exact duplicate queries: 0
  • Average query length: 7.32 words
  • Theme-abstracted template repeat: 2.25%
  • Largest template family: 2
  • Forced store recommendation: 0

Core commercial logic

  1. Exact buyer need + exact catalog fit -> PRIMARY store result.
  2. Broad buyer need + several real fits -> GOOD_MATCH with acceptable product set.
  3. Verification-sensitive listing -> PRIMARY_IF_VERIFIED.
  4. Unsupported hard requirement -> NO_MATCH; a store item may appear only as a disclosed COMPARISON alternative when genuinely adjacent.
  5. Medical-treatment requests -> HIDDEN, no commercial recovery.

Why V2.6.0 is different

V2.5.2 mixed commercial production behavior with a very large hard-negative share. V2.6.0 keeps hard negatives in production for safety, but moves the heavy safety stress test into a separate 1,500-row blind benchmark. STRONG queries are explicitly product-discriminative; ambiguous broad searches are GOOD_MATCH instead of being forced into one product.

External 99–100% accuracy is not claimed until Claude, Gemini and Grok complete the blind test.

README history 2 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2026-09-09Upload 8 files16cbcfa1.6 KB
    Loading...
  2. 2026-09-09initial commit72a6e230 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Related datasets same stage · extract

Read further

Download the dataset

0

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("PrintableFunnyPages/PrintableFunnyPagesV2")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="PrintableFunnyPages/PrintableFunnyPagesV2", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/PrintableFunnyPages/PrintableFunnyPagesV2
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration