Datasetpublic

316usman/customer-ticket-resolution

CUSTOMER_TICKET_RESOLUTION A preference dataset for CUSTOMER_TICKET_RESOLUTION, harvested from real, human-labelled sources and curated by an automated harvesting harness with an LLM quality gate. Format Standard preference / DPO schema — each row: column meaning prompt the request (originally ticket) chosen the human-preferred response rejected a worse response to the same prompt source the dataset/URL the row was harvested from… See the full description on the dataset page: https://huggingface.co/datasets/316usman/customer-ticket-resolution.

sourceHugging Faceunknownupdated 15d agoView on Hugging Face

0likes79downloads

Dataset Card

CUSTOMERTICKETRESOLUTION

A preference dataset for CUSTOMER_TICKET_RESOLUTION, harvested from real, human-labelled sources and curated by an automated harvesting harness with an LLM quality gate.

Format

Standard preference / DPO schema — each row:

column	meaning
`prompt`	the request (originally `ticket`)
`chosen`	the human-preferred response
`rejected`	a worse response to the same prompt
`source`	the dataset/URL the row was harvested from

Splits

80/10/10 train / validation / test (seeded shuffle): train:1612 / validation:201 / test:203

Stats

—Rows: 2016
—Distinct sources: 3

Sources

—Lakshan2003/customer-support-client-agent-conversations
—NebulaByte/E-Commerce_Customer_Support_Conversations
—Tobi-Bueck/customer-support-tickets

Provenance

Each row's chosen/rejected distinction comes from a real human signal (upvotes, accepted answers, ratings, or a real strong-vs-weak reply). Rows passed an automated quality gate checking that chosen is a clean response (not a transcript), the chosen/rejected contrast is about quality (not length), and the row is on-intent.