Datasets:
id stringlengths 33 75 | group_id stringlengths 24 53 | split stringclasses 1
value | source stringclasses 12
values | kind stringclasses 3
values | question stringlengths 38 926 | options listlengths 2 16 | target listlengths 2 16 | state_json stringlengths 187 1.26k | metadata_json stringlengths 462 975 | record_json stringlengths 999 3.03k | original_line_number int64 1 80.8k |
|---|---|---|---|---|---|---|---|---|---|---|---|
customer-control-v1:42:1:category | customer-control-v1:42:1 | train | customer-control-v1 | choice | Determine the broad category of this support ticket. For this controlled task, select the customer's expressly prioritized request. If two requests explicitly have equal priority, allocate equal support to their two categories. A malfunction of an existing feature is bug_report; a payment or refund request is billing; ... | [
"account: Login, permissions, profile, security",
"bug_report: The user is reporting something that is broken or producing errors",
"billing: Charges, invoices, refunds, subscriptions",
"feature_request: The user is requesting new functionality"
] | [
1,
0,
0,
0
] | "Conversation with account holder Harbor-65673ba098.\nCustomer message: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: This is frustrating, but I appreciate your help and will keep this construct... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-65673ba098"], "family": "routing", "language": "en", "provenance": {"annotation_status": "synthetic_c... | {"group_id": "customer-control-v1:42:1", "id": "customer-control-v1:42:1:category", "kind": "choice", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_id... | 1 |
customer-control-v1:42:1:bug_severity | customer-control-v1:42:1 | train | customer-control-v1 | score | How severe is the reported issue? Use the stated functional impact and the existence of a workaround. Use no functional impact when no malfunction is described. In this synthetic control, if a broken feature is described but the availability of a workaround is explicitly unknown, the two latent possibilities (workaroun... | [
"Cosmetic; no impact to functionality",
"Broken or degraded feature; workaround exists",
"Blocking issue; no workaround exists"
] | [
1,
0,
0
] | "Conversation with account holder Harbor-65673ba098.\nCustomer message: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: This is frustrating, but I appreciate your help and will keep this construct... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-65673ba098"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic_co... | {"group_id": "customer-control-v1:42:1", "id": "customer-control-v1:42:1:bug_severity", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity... | 2 |
customer-control-v1:42:1:has_reproducible_steps | customer-control-v1:42:1 | train | customer-control-v1 | noul | The user describes specific steps to reproduce the issue. For this controlled task, require at least two ordered user actions and the observed result. A vague report, a resolved historical issue, or an instruction to support staff is insufficient. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-65673ba098.\nCustomer message: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: This is frustrating, but I appreciate your help and will keep this construct... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-65673ba098"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "synthetic_... | {"group_id": "customer-control-v1:42:1", "id": "customer-control-v1:42:1:has_reproducible_steps", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}... | 3 |
customer-control-v1:42:1:refund_requested | customer-control-v1:42:1 | train | customer-control-v1 | noul | The user is explicitly asking for a refund or credit for the current issue. A question about charges, an explicit denial of wanting money back, or a mention of an already completed refund is not a current request. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-65673ba098.\nCustomer message: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: This is frustrating, but I appreciate your help and will keep this construct... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-65673ba098"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "synthetic_... | {"group_id": "customer-control-v1:42:1", "id": "customer-control-v1:42:1:refund_requested", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "ent... | 4 |
customer-control-v1:42:1:frustration | customer-control-v1:42:1 | train | customer-control-v1 | score | How frustrated the user appears. Use the current expressed tone. For a reaction that carries no clear emotional valence, the controlled generator has two equally likely latent readings: calm or frustrated but civil. Do not infer very angry without an explicit anger signal. | [
"Calm, matter-of-fact",
"Frustrated but civil",
"Very angry"
] | [
0,
1,
0
] | "Conversation with account holder Harbor-65673ba098.\nCustomer message: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: This is frustrating, but I appreciate your help and will keep this construct... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-65673ba098"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic_co... | {"group_id": "customer-control-v1:42:1", "id": "customer-control-v1:42:1:frustration", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_... | 5 |
customer-control-v1:42:1:churn_likelihood_level | customer-control-v1:42:1 | train | customer-control-v1 | score | Churn likelihood level. This is a local ordinal intention rubric, not an empirically calibrated prediction of future churn. Evaluate the customer's stated continuation intent. If intent was explicitly withheld or not discussed, the synthetic generator has three equally likely latent intention levels. | [
"The customer explicitly intends to keep using the service and continue their subscription.",
"The customer is undecided about continuing, or makes departure conditional on whether the issue is resolved.",
"The customer explicitly requests cancellation or states a definite decision to stop using the service."
] | [
0,
1,
0
] | "Conversation with account holder Harbor-65673ba098.\nCustomer message: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: This is frustrating, but I appreciate your help and will keep this construct... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-65673ba098"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic_co... | {"group_id": "customer-control-v1:42:1", "id": "customer-control-v1:42:1:churn_likelihood_level", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0... | 6 |
customer-control-v1:42:2:category | customer-control-v1:42:2 | train | customer-control-v1 | choice | Determine the broad category of this support ticket. For this controlled task, select the customer's expressly prioritized request. If two requests explicitly have equal priority, allocate equal support to their two categories. A malfunction of an existing feature is bug_report; a payment or refund request is billing; ... | [
"feature_request: The user is requesting new functionality",
"bug_report: The user is reporting something that is broken or producing errors",
"account: Login, permissions, profile, security",
"billing: Charges, invoices, refunds, subscriptions"
] | [
0,
1,
0,
0
] | "Conversation with account holder Harbor-171ebedb3f.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-171ebedb3f"], "family": "routing", "language": "en", "provenance": {"annotation_status": "s... | {"group_id": "customer-control-v1:42:2", "id": "customer-control-v1:42:2:category", "kind": "choice", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2}, ... | 7 |
customer-control-v1:42:2:bug_severity | customer-control-v1:42:2 | train | customer-control-v1 | score | How severe is the reported issue? Use the stated functional impact and the existence of a workaround. Use no functional impact when no malfunction is described. In this synthetic control, if a broken feature is described but the availability of a workaround is explicitly unknown, the two latent possibilities (workaroun... | [
"Cosmetic; no impact to functionality",
"Broken or degraded feature; workaround exists",
"Blocking issue; no workaround exists"
] | [
0,
0.5,
0.5
] | "Conversation with account holder Harbor-171ebedb3f.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-171ebedb3f"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "sy... | {"group_id": "customer-control-v1:42:2", "id": "customer-control-v1:42:2:bug_severity", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2... | 8 |
customer-control-v1:42:2:has_reproducible_steps | customer-control-v1:42:2 | train | customer-control-v1 | noul | The user describes specific steps to reproduce the issue. For this controlled task, require at least two ordered user actions and the observed result. A vague report, a resolved historical issue, or an instruction to support staff is insufficient. | [
"no",
"yes"
] | [
0,
1
] | "Conversation with account holder Harbor-171ebedb3f.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-171ebedb3f"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "... | {"group_id": "customer-control-v1:42:2", "id": "customer-control-v1:42:2:has_reproducible_steps", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "sev... | 9 |
customer-control-v1:42:2:refund_requested | customer-control-v1:42:2 | train | customer-control-v1 | noul | The user is explicitly asking for a refund or credit for the current issue. A question about charges, an explicit denial of wanting money back, or a mention of an already completed refund is not a current request. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-171ebedb3f.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-171ebedb3f"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "... | {"group_id": "customer-control-v1:42:2", "id": "customer-control-v1:42:2:refund_requested", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity"... | 10 |
customer-control-v1:42:2:frustration | customer-control-v1:42:2 | train | customer-control-v1 | score | How frustrated the user appears. Use the current expressed tone. For a reaction that carries no clear emotional valence, the controlled generator has two equally likely latent readings: calm or frustrated but civil. Do not infer very angry without an explicit anger signal. | [
"Calm, matter-of-fact",
"Frustrated but civil",
"Very angry"
] | [
0,
1,
0
] | "Conversation with account holder Harbor-171ebedb3f.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-171ebedb3f"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "sy... | {"group_id": "customer-control-v1:42:2", "id": "customer-control-v1:42:2:frustration", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2}... | 11 |
customer-control-v1:42:2:churn_likelihood_level | customer-control-v1:42:2 | train | customer-control-v1 | score | Churn likelihood level. This is a local ordinal intention rubric, not an empirically calibrated prediction of future churn. Evaluate the customer's stated continuation intent. If intent was explicitly withheld or not discussed, the synthetic generator has three equally likely latent intention levels. | [
"The customer explicitly intends to keep using the service and continue their subscription.",
"The customer is undecided about continuing, or makes departure conditional on whether the issue is resolved.",
"The customer explicitly requests cancellation or states a definite decision to stop using the service."
] | [
0,
0,
1
] | "Conversation with account holder Harbor-171ebedb3f.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-171ebedb3f"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "sy... | {"group_id": "customer-control-v1:42:2", "id": "customer-control-v1:42:2:churn_likelihood_level", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 2, "frustration": 1, "refund": false, "repro": true, "se... | 12 |
customer-control-v1:42:3:category | customer-control-v1:42:3 | train | customer-control-v1 | choice | Determine the broad category of this support ticket. For this controlled task, select the customer's expressly prioritized request. If two requests explicitly have equal priority, allocate equal support to their two categories. A malfunction of an existing feature is bug_report; a payment or refund request is billing; ... | [
"bug_report: The user is reporting something that is broken or producing errors",
"billing: Charges, invoices, refunds, subscriptions",
"account: Login, permissions, profile, security",
"feature_request: The user is requesting new functionality"
] | [
1,
0,
0,
0
] | "Customer Harbor-7e3fd7035c: Report export fails through every available method, so I cannot complete my filing. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: It happens sometimes, but I cannot recall the sequence that led to it. I am furious. This treatment is outrageous... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 2}, "entity_ids": ["Harbor-7e3fd7035c"], "family": "routing", "language": "en", "provenance": {"annotation_... | {"group_id": "customer-control-v1:42:3", "id": "customer-control-v1:42:3:category", "kind": "choice", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "seve... | 13 |
customer-control-v1:42:3:bug_severity | customer-control-v1:42:3 | train | customer-control-v1 | score | How severe is the reported issue? Use the stated functional impact and the existence of a workaround. Use no functional impact when no malfunction is described. In this synthetic control, if a broken feature is described but the availability of a workaround is explicitly unknown, the two latent possibilities (workaroun... | [
"Cosmetic; no impact to functionality",
"Broken or degraded feature; workaround exists",
"Blocking issue; no workaround exists"
] | [
0,
0,
1
] | "Customer Harbor-7e3fd7035c: Report export fails through every available method, so I cannot complete my filing. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: It happens sometimes, but I cannot recall the sequence that led to it. I am furious. This treatment is outrageous... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 2}, "entity_ids": ["Harbor-7e3fd7035c"], "family": "rubric", "language": "en", "provenance": {"annotation_s... | {"group_id": "customer-control-v1:42:3", "id": "customer-control-v1:42:3:bug_severity", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "s... | 14 |
customer-control-v1:42:3:has_reproducible_steps | customer-control-v1:42:3 | train | customer-control-v1 | noul | The user describes specific steps to reproduce the issue. For this controlled task, require at least two ordered user actions and the observed result. A vague report, a resolved historical issue, or an instruction to support staff is insufficient. | [
"no",
"yes"
] | [
1,
0
] | "Customer Harbor-7e3fd7035c: Report export fails through every available method, so I cannot complete my filing. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: It happens sometimes, but I cannot recall the sequence that led to it. I am furious. This treatment is outrageous... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 2}, "entity_ids": ["Harbor-7e3fd7035c"], "family": "evidence", "language": "en", "provenance": {"annotation... | {"group_id": "customer-control-v1:42:3", "id": "customer-control-v1:42:3:has_reproducible_steps", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": ... | 15 |
customer-control-v1:42:3:refund_requested | customer-control-v1:42:3 | train | customer-control-v1 | noul | The user is explicitly asking for a refund or credit for the current issue. A question about charges, an explicit denial of wanting money back, or a mention of an already completed refund is not a current request. | [
"no",
"yes"
] | [
1,
0
] | "Customer Harbor-7e3fd7035c: Report export fails through every available method, so I cannot complete my filing. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: It happens sometimes, but I cannot recall the sequence that led to it. I am furious. This treatment is outrageous... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 2}, "entity_ids": ["Harbor-7e3fd7035c"], "family": "evidence", "language": "en", "provenance": {"annotation... | {"group_id": "customer-control-v1:42:3", "id": "customer-control-v1:42:3:refund_requested", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false,... | 16 |
customer-control-v1:42:3:frustration | customer-control-v1:42:3 | train | customer-control-v1 | score | How frustrated the user appears. Use the current expressed tone. For a reaction that carries no clear emotional valence, the controlled generator has two equally likely latent readings: calm or frustrated but civil. Do not infer very angry without an explicit anger signal. | [
"Calm, matter-of-fact",
"Frustrated but civil",
"Very angry"
] | [
0,
0,
1
] | "Customer Harbor-7e3fd7035c: Report export fails through every available method, so I cannot complete my filing. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: It happens sometimes, but I cannot recall the sequence that led to it. I am furious. This treatment is outrageous... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 2}, "entity_ids": ["Harbor-7e3fd7035c"], "family": "rubric", "language": "en", "provenance": {"annotation_s... | {"group_id": "customer-control-v1:42:3", "id": "customer-control-v1:42:3:frustration", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "se... | 17 |
customer-control-v1:42:3:churn_likelihood_level | customer-control-v1:42:3 | train | customer-control-v1 | score | Churn likelihood level. This is a local ordinal intention rubric, not an empirically calibrated prediction of future churn. Evaluate the customer's stated continuation intent. If intent was explicitly withheld or not discussed, the synthetic generator has three equally likely latent intention levels. | [
"The customer explicitly intends to keep using the service and continue their subscription.",
"The customer is undecided about continuing, or makes departure conditional on whether the issue is resolved.",
"The customer explicitly requests cancellation or states a definite decision to stop using the service."
] | [
0.3333333333333333,
0.3333333333333333,
0.3333333333333333
] | "Customer Harbor-7e3fd7035c: Report export fails through every available method, so I cannot complete my filing. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: It happens sometimes, but I cannot recall the sequence that led to it. I am furious. This treatment is outrageous... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 2}, "entity_ids": ["Harbor-7e3fd7035c"], "family": "rubric", "language": "en", "provenance": {"annotation_s... | {"group_id": "customer-control-v1:42:3", "id": "customer-control-v1:42:3:churn_likelihood_level", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "churn_likelihood_level", "categories": ["bug_report"], "churn": 2, "frustration": 2, "refund": false, "repro":... | 18 |
customer-control-v1:42:4:category | customer-control-v1:42:4 | train | customer-control-v1 | choice | Determine the broad category of this support ticket. For this controlled task, select the customer's expressly prioritized request. If two requests explicitly have equal priority, allocate equal support to their two categories. A malfunction of an existing feature is bug_report; a payment or refund request is billing; ... | [
"feature_request: The user is requesting new functionality",
"bug_report: The user is reporting something that is broken or producing errors",
"account: Login, permissions, profile, security",
"billing: Charges, invoices, refunds, subscriptions"
] | [
0,
1,
0,
0
] | "Conversation with account holder Harbor-f24d8a39ef.\nCustomer message: Exporting a report fails, but I can download the CSV and finish in the desktop app. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: It happens sometimes, but I cannot recall the sequence that led t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "entity_ids": ["Harbor-f24d8a39ef"], "family": "routing", "language": "en", "provenance": {"annotation_status": "syntheti... | {"group_id": "customer-control-v1:42:4", "id": "customer-control-v1:42:4:category", "kind": "choice", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "entity... | 19 |
customer-control-v1:42:4:bug_severity | customer-control-v1:42:4 | train | customer-control-v1 | score | How severe is the reported issue? Use the stated functional impact and the existence of a workaround. Use no functional impact when no malfunction is described. In this synthetic control, if a broken feature is described but the availability of a workaround is explicitly unknown, the two latent possibilities (workaroun... | [
"Cosmetic; no impact to functionality",
"Broken or degraded feature; workaround exists",
"Blocking issue; no workaround exists"
] | [
0,
1,
0
] | "Conversation with account holder Harbor-f24d8a39ef.\nCustomer message: Exporting a report fails, but I can download the CSV and finish in the desktop app. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: It happens sometimes, but I cannot recall the sequence that led t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "entity_ids": ["Harbor-f24d8a39ef"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic... | {"group_id": "customer-control-v1:42:4", "id": "customer-control-v1:42:4:bug_severity", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "ent... | 20 |
customer-control-v1:42:4:has_reproducible_steps | customer-control-v1:42:4 | train | customer-control-v1 | noul | The user describes specific steps to reproduce the issue. For this controlled task, require at least two ordered user actions and the observed result. A vague report, a resolved historical issue, or an instruction to support staff is insufficient. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-f24d8a39ef.\nCustomer message: Exporting a report fails, but I can download the CSV and finish in the desktop app. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: It happens sometimes, but I cannot recall the sequence that led t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "entity_ids": ["Harbor-f24d8a39ef"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "synthet... | {"group_id": "customer-control-v1:42:4", "id": "customer-control-v1:42:4:has_reproducible_steps", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity":... | 21 |
customer-control-v1:42:4:refund_requested | customer-control-v1:42:4 | train | customer-control-v1 | noul | The user is explicitly asking for a refund or credit for the current issue. A question about charges, an explicit denial of wanting money back, or a mention of an already completed refund is not a current request. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-f24d8a39ef.\nCustomer message: Exporting a report fails, but I can download the CSV and finish in the desktop app. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: It happens sometimes, but I cannot recall the sequence that led t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "entity_ids": ["Harbor-f24d8a39ef"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "synthet... | {"group_id": "customer-control-v1:42:4", "id": "customer-control-v1:42:4:refund_requested", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "... | 22 |
customer-control-v1:42:4:frustration | customer-control-v1:42:4 | train | customer-control-v1 | score | How frustrated the user appears. Use the current expressed tone. For a reaction that carries no clear emotional valence, the controlled generator has two equally likely latent readings: calm or frustrated but civil. Do not infer very angry without an explicit anger signal. | [
"Calm, matter-of-fact",
"Frustrated but civil",
"Very angry"
] | [
0,
0,
1
] | "Conversation with account holder Harbor-f24d8a39ef.\nCustomer message: Exporting a report fails, but I can download the CSV and finish in the desktop app. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: It happens sometimes, but I cannot recall the sequence that led t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "entity_ids": ["Harbor-f24d8a39ef"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic... | {"group_id": "customer-control-v1:42:4", "id": "customer-control-v1:42:4:frustration", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "enti... | 23 |
customer-control-v1:42:4:churn_likelihood_level | customer-control-v1:42:4 | train | customer-control-v1 | score | Churn likelihood level. This is a local ordinal intention rubric, not an empirically calibrated prediction of future churn. Evaluate the customer's stated continuation intent. If intent was explicitly withheld or not discussed, the synthetic generator has three equally likely latent intention levels. | [
"The customer explicitly intends to keep using the service and continue their subscription.",
"The customer is undecided about continuing, or makes departure conditional on whether the issue is resolved.",
"The customer explicitly requests cancellation or states a definite decision to stop using the service."
] | [
1,
0,
0
] | "Conversation with account holder Harbor-f24d8a39ef.\nCustomer message: Exporting a report fails, but I can download the CSV and finish in the desktop app. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: It happens sometimes, but I cannot recall the sequence that led t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity": 1}, "entity_ids": ["Harbor-f24d8a39ef"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic... | {"group_id": "customer-control-v1:42:4", "id": "customer-control-v1:42:4:churn_likelihood_level", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": false, "severity"... | 24 |
customer-control-v1:42:5:category | customer-control-v1:42:5 | train | customer-control-v1 | choice | Determine the broad category of this support ticket. For this controlled task, select the customer's expressly prioritized request. If two requests explicitly have equal priority, allocate equal support to their two categories. A malfunction of an existing feature is bug_report; a payment or refund request is billing; ... | [
"account: Login, permissions, profile, security",
"feature_request: The user is requesting new functionality",
"bug_report: The user is reporting something that is broken or producing errors",
"billing: Charges, invoices, refunds, subscriptions"
] | [
0,
1,
0,
0
] | "Conversation with account holder Harbor-c57379e129.\nCustomer message: I would like an offline reading mode, which this product does not currently offer. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I am furious. This treatment is outrageous and completely unaccept... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-c57379e129"], "family": "routing", "language": "en", "provenance": {"annotation_status": "syn... | {"group_id": "customer-control-v1:42:5", "id": "customer-control-v1:42:5:category", "kind": "choice", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0}, "e... | 25 |
customer-control-v1:42:5:bug_severity | customer-control-v1:42:5 | train | customer-control-v1 | score | How severe is the reported issue? Use the stated functional impact and the existence of a workaround. Use no functional impact when no malfunction is described. In this synthetic control, if a broken feature is described but the availability of a workaround is explicitly unknown, the two latent possibilities (workaroun... | [
"Cosmetic; no impact to functionality",
"Broken or degraded feature; workaround exists",
"Blocking issue; no workaround exists"
] | [
1,
0,
0
] | "Conversation with account holder Harbor-c57379e129.\nCustomer message: I would like an offline reading mode, which this product does not currently offer. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I am furious. This treatment is outrageous and completely unaccept... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-c57379e129"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synt... | {"group_id": "customer-control-v1:42:5", "id": "customer-control-v1:42:5:bug_severity", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0},... | 26 |
customer-control-v1:42:5:has_reproducible_steps | customer-control-v1:42:5 | train | customer-control-v1 | noul | The user describes specific steps to reproduce the issue. For this controlled task, require at least two ordered user actions and the observed result. A vague report, a resolved historical issue, or an instruction to support staff is insufficient. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-c57379e129.\nCustomer message: I would like an offline reading mode, which this product does not currently offer. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I am furious. This treatment is outrageous and completely unaccept... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-c57379e129"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "sy... | {"group_id": "customer-control-v1:42:5", "id": "customer-control-v1:42:5:has_reproducible_steps", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "sever... | 27 |
customer-control-v1:42:5:refund_requested | customer-control-v1:42:5 | train | customer-control-v1 | noul | The user is explicitly asking for a refund or credit for the current issue. A question about charges, an explicit denial of wanting money back, or a mention of an already completed refund is not a current request. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-c57379e129.\nCustomer message: I would like an offline reading mode, which this product does not currently offer. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I am furious. This treatment is outrageous and completely unaccept... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-c57379e129"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "sy... | {"group_id": "customer-control-v1:42:5", "id": "customer-control-v1:42:5:refund_requested", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": ... | 28 |
customer-control-v1:42:5:frustration | customer-control-v1:42:5 | train | customer-control-v1 | score | How frustrated the user appears. Use the current expressed tone. For a reaction that carries no clear emotional valence, the controlled generator has two equally likely latent readings: calm or frustrated but civil. Do not infer very angry without an explicit anger signal. | [
"Calm, matter-of-fact",
"Frustrated but civil",
"Very angry"
] | [
0,
0,
1
] | "Conversation with account holder Harbor-c57379e129.\nCustomer message: I would like an offline reading mode, which this product does not currently offer. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I am furious. This treatment is outrageous and completely unaccept... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-c57379e129"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synt... | {"group_id": "customer-control-v1:42:5", "id": "customer-control-v1:42:5:frustration", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0}, ... | 29 |
customer-control-v1:42:5:churn_likelihood_level | customer-control-v1:42:5 | train | customer-control-v1 | score | Churn likelihood level. This is a local ordinal intention rubric, not an empirically calibrated prediction of future churn. Evaluate the customer's stated continuation intent. If intent was explicitly withheld or not discussed, the synthetic generator has three equally likely latent intention levels. | [
"The customer explicitly intends to keep using the service and continue their subscription.",
"The customer is undecided about continuing, or makes departure conditional on whether the issue is resolved.",
"The customer explicitly requests cancellation or states a definite decision to stop using the service."
] | [
0,
0,
1
] | "Conversation with account holder Harbor-c57379e129.\nCustomer message: I would like an offline reading mode, which this product does not currently offer. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I am furious. This treatment is outrageous and completely unaccept... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-c57379e129"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synt... | {"group_id": "customer-control-v1:42:5", "id": "customer-control-v1:42:5:churn_likelihood_level", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["feature_request"], "churn": 2, "frustration": 2, "refund": false, "repro": false, "seve... | 30 |
customer-control-v1:42:6:category | customer-control-v1:42:6 | train | customer-control-v1 | choice | Determine the broad category of this support ticket. For this controlled task, select the customer's expressly prioritized request. If two requests explicitly have equal priority, allocate equal support to their two categories. A malfunction of an existing feature is bug_report; a payment or refund request is billing; ... | [
"billing: Charges, invoices, refunds, subscriptions",
"account: Login, permissions, profile, security",
"bug_report: The user is reporting something that is broken or producing errors",
"feature_request: The user is requesting new functionality"
] | [
1,
0,
0,
0
] | "Conversation with account holder Harbor-b61817726d.\nCustomer message: My card was charged twice for the same monthly invoice. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: Please explain this charge; I am not asking for money back. This is frustrating, but I apprec... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-b61817726d"], "family": "routing", "language": "en", "provenance": {"annotation_status": "synthetic_c... | {"group_id": "customer-control-v1:42:6", "id": "customer-control-v1:42:6:category", "kind": "choice", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_id... | 31 |
customer-control-v1:42:6:bug_severity | customer-control-v1:42:6 | train | customer-control-v1 | score | How severe is the reported issue? Use the stated functional impact and the existence of a workaround. Use no functional impact when no malfunction is described. In this synthetic control, if a broken feature is described but the availability of a workaround is explicitly unknown, the two latent possibilities (workaroun... | [
"Cosmetic; no impact to functionality",
"Broken or degraded feature; workaround exists",
"Blocking issue; no workaround exists"
] | [
1,
0,
0
] | "Conversation with account holder Harbor-b61817726d.\nCustomer message: My card was charged twice for the same monthly invoice. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: Please explain this charge; I am not asking for money back. This is frustrating, but I apprec... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-b61817726d"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic_co... | {"group_id": "customer-control-v1:42:6", "id": "customer-control-v1:42:6:bug_severity", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity... | 32 |
customer-control-v1:42:6:has_reproducible_steps | customer-control-v1:42:6 | train | customer-control-v1 | noul | The user describes specific steps to reproduce the issue. For this controlled task, require at least two ordered user actions and the observed result. A vague report, a resolved historical issue, or an instruction to support staff is insufficient. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-b61817726d.\nCustomer message: My card was charged twice for the same monthly invoice. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: Please explain this charge; I am not asking for money back. This is frustrating, but I apprec... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-b61817726d"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "synthetic_... | {"group_id": "customer-control-v1:42:6", "id": "customer-control-v1:42:6:has_reproducible_steps", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}... | 33 |
customer-control-v1:42:6:refund_requested | customer-control-v1:42:6 | train | customer-control-v1 | noul | The user is explicitly asking for a refund or credit for the current issue. A question about charges, an explicit denial of wanting money back, or a mention of an already completed refund is not a current request. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-b61817726d.\nCustomer message: My card was charged twice for the same monthly invoice. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: Please explain this charge; I am not asking for money back. This is frustrating, but I apprec... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-b61817726d"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "synthetic_... | {"group_id": "customer-control-v1:42:6", "id": "customer-control-v1:42:6:refund_requested", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "ent... | 34 |
customer-control-v1:42:6:frustration | customer-control-v1:42:6 | train | customer-control-v1 | score | How frustrated the user appears. Use the current expressed tone. For a reaction that carries no clear emotional valence, the controlled generator has two equally likely latent readings: calm or frustrated but civil. Do not infer very angry without an explicit anger signal. | [
"Calm, matter-of-fact",
"Frustrated but civil",
"Very angry"
] | [
0,
1,
0
] | "Conversation with account holder Harbor-b61817726d.\nCustomer message: My card was charged twice for the same monthly invoice. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: Please explain this charge; I am not asking for money back. This is frustrating, but I apprec... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-b61817726d"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic_co... | {"group_id": "customer-control-v1:42:6", "id": "customer-control-v1:42:6:frustration", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_... | 35 |
customer-control-v1:42:6:churn_likelihood_level | customer-control-v1:42:6 | train | customer-control-v1 | score | Churn likelihood level. This is a local ordinal intention rubric, not an empirically calibrated prediction of future churn. Evaluate the customer's stated continuation intent. If intent was explicitly withheld or not discussed, the synthetic generator has three equally likely latent intention levels. | [
"The customer explicitly intends to keep using the service and continue their subscription.",
"The customer is undecided about continuing, or makes departure conditional on whether the issue is resolved.",
"The customer explicitly requests cancellation or states a definite decision to stop using the service."
] | [
0,
1,
0
] | "Conversation with account holder Harbor-b61817726d.\nCustomer message: My card was charged twice for the same monthly invoice. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: Please explain this charge; I am not asking for money back. This is frustrating, but I apprec... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-b61817726d"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic_co... | {"group_id": "customer-control-v1:42:6", "id": "customer-control-v1:42:6:churn_likelihood_level", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["billing"], "churn": 1, "frustration": 1, "refund": false, "repro": false, "severity": 0... | 36 |
customer-control-v1:42:7:category | customer-control-v1:42:7 | train | customer-control-v1 | choice | Determine the broad category of this support ticket. For this controlled task, select the customer's expressly prioritized request. If two requests explicitly have equal priority, allocate equal support to their two categories. A malfunction of an existing feature is bug_report; a payment or refund request is billing; ... | [
"account: Login, permissions, profile, security",
"bug_report: The user is reporting something that is broken or producing errors",
"billing: Charges, invoices, refunds, subscriptions",
"feature_request: The user is requesting new functionality"
] | [
0,
1,
0,
0
] | "Conversation with account holder Harbor-3ca9e8a3f3.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-3ca9e8a3f3"], "family": "routing", "language": "en", "provenance": {"annotation_status": "s... | {"group_id": "customer-control-v1:42:7", "id": "customer-control-v1:42:7:category", "kind": "choice", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2}, ... | 37 |
customer-control-v1:42:7:bug_severity | customer-control-v1:42:7 | train | customer-control-v1 | score | How severe is the reported issue? Use the stated functional impact and the existence of a workaround. Use no functional impact when no malfunction is described. In this synthetic control, if a broken feature is described but the availability of a workaround is explicitly unknown, the two latent possibilities (workaroun... | [
"Cosmetic; no impact to functionality",
"Broken or degraded feature; workaround exists",
"Blocking issue; no workaround exists"
] | [
0,
0.5,
0.5
] | "Conversation with account holder Harbor-3ca9e8a3f3.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-3ca9e8a3f3"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "sy... | {"group_id": "customer-control-v1:42:7", "id": "customer-control-v1:42:7:bug_severity", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2... | 38 |
customer-control-v1:42:7:has_reproducible_steps | customer-control-v1:42:7 | train | customer-control-v1 | noul | The user describes specific steps to reproduce the issue. For this controlled task, require at least two ordered user actions and the observed result. A vague report, a resolved historical issue, or an instruction to support staff is insufficient. | [
"no",
"yes"
] | [
0,
1
] | "Conversation with account holder Harbor-3ca9e8a3f3.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-3ca9e8a3f3"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "... | {"group_id": "customer-control-v1:42:7", "id": "customer-control-v1:42:7:has_reproducible_steps", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "sev... | 39 |
customer-control-v1:42:7:refund_requested | customer-control-v1:42:7 | train | customer-control-v1 | noul | The user is explicitly asking for a refund or credit for the current issue. A question about charges, an explicit denial of wanting money back, or a mention of an already completed refund is not a current request. | [
"no",
"yes"
] | [
1,
0
] | "Conversation with account holder Harbor-3ca9e8a3f3.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-3ca9e8a3f3"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "... | {"group_id": "customer-control-v1:42:7", "id": "customer-control-v1:42:7:refund_requested", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity"... | 40 |
customer-control-v1:42:7:frustration | customer-control-v1:42:7 | train | customer-control-v1 | score | How frustrated the user appears. Use the current expressed tone. For a reaction that carries no clear emotional valence, the controlled generator has two equally likely latent readings: calm or frustrated but civil. Do not infer very angry without an explicit anger signal. | [
"Calm, matter-of-fact",
"Frustrated but civil",
"Very angry"
] | [
0,
0,
1
] | "Conversation with account holder Harbor-3ca9e8a3f3.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-3ca9e8a3f3"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "sy... | {"group_id": "customer-control-v1:42:7", "id": "customer-control-v1:42:7:frustration", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2}... | 41 |
customer-control-v1:42:7:churn_likelihood_level | customer-control-v1:42:7 | train | customer-control-v1 | score | Churn likelihood level. This is a local ordinal intention rubric, not an empirically calibrated prediction of future churn. Evaluate the customer's stated continuation intent. If intent was explicitly withheld or not discussed, the synthetic generator has three equally likely latent intention levels. | [
"The customer explicitly intends to keep using the service and continue their subscription.",
"The customer is undecided about continuing, or makes departure conditional on whether the issue is resolved.",
"The customer explicitly requests cancellation or states a definite decision to stop using the service."
] | [
1,
0,
0
] | "Conversation with account holder Harbor-3ca9e8a3f3.\nCustomer message: Exporting a report fails. I haven't tested the desktop route and don't know whether an alternative works. That is the request I want you to handle first.\nSupport: Please tell us more.\nCustomer response: I open a saved report, then click Export; t... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "severity": 2}, "entity_ids": ["Harbor-3ca9e8a3f3"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "sy... | {"group_id": "customer-control-v1:42:7", "id": "customer-control-v1:42:7:churn_likelihood_level", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "bug_severity", "categories": ["bug_report"], "churn": 0, "frustration": 2, "refund": false, "repro": true, "se... | 42 |
customer-control-v1:42:8:category | customer-control-v1:42:8 | train | customer-control-v1 | choice | Determine the broad category of this support ticket. For this controlled task, select the customer's expressly prioritized request. If two requests explicitly have equal priority, allocate equal support to their two categories. A malfunction of an existing feature is bug_report; a payment or refund request is billing; ... | [
"bug_report: The user is reporting something that is broken or producing errors",
"billing: Charges, invoices, refunds, subscriptions",
"feature_request: The user is requesting new functionality",
"account: Login, permissions, profile, security"
] | [
0,
0,
0,
1
] | "Customer Harbor-a63912706e: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: This is frustrating, but I appreciate your help and will keep this constructive. I have decided to leave. Please cancel my s... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 2, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-a63912706e"], "family": "routing", "language": "en", "provenance": {"annotation_status": "synthetic_c... | {"group_id": "customer-control-v1:42:8", "id": "customer-control-v1:42:8:category", "kind": "choice", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 2, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_id... | 43 |
customer-control-v1:42:8:bug_severity | customer-control-v1:42:8 | train | customer-control-v1 | score | How severe is the reported issue? Use the stated functional impact and the existence of a workaround. Use no functional impact when no malfunction is described. In this synthetic control, if a broken feature is described but the availability of a workaround is explicitly unknown, the two latent possibilities (workaroun... | [
"Cosmetic; no impact to functionality",
"Broken or degraded feature; workaround exists",
"Blocking issue; no workaround exists"
] | [
1,
0,
0
] | "Customer Harbor-a63912706e: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: This is frustrating, but I appreciate your help and will keep this constructive. I have decided to leave. Please cancel my s... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 2, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-a63912706e"], "family": "rubric", "language": "en", "provenance": {"annotation_status": "synthetic_co... | {"group_id": "customer-control-v1:42:8", "id": "customer-control-v1:42:8:bug_severity", "kind": "score", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 2, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity... | 44 |
customer-control-v1:42:8:has_reproducible_steps | customer-control-v1:42:8 | train | customer-control-v1 | noul | The user describes specific steps to reproduce the issue. For this controlled task, require at least two ordered user actions and the observed result. A vague report, a resolved historical issue, or an instruction to support staff is insufficient. | [
"no",
"yes"
] | [
1,
0
] | "Customer Harbor-a63912706e: I need access restored after changing the email address used to sign in. That is the request I want you to handle first.\nAgent: Could you add the details?\nCustomer: This is frustrating, but I appreciate your help and will keep this constructive. I have decided to leave. Please cancel my s... | {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 2, "frustration": 1, "refund": false, "repro": false, "severity": 0}, "entity_ids": ["Harbor-a63912706e"], "family": "evidence", "language": "en", "provenance": {"annotation_status": "synthetic_... | {"group_id": "customer-control-v1:42:8", "id": "customer-control-v1:42:8:has_reproducible_steps", "kind": "noul", "metadata": {"case_name": "customer_support_fanout_control", "control_latents": {"ambiguity": "none", "categories": ["account"], "churn": 2, "frustration": 1, "refund": false, "repro": false, "severity": 0}... | 45 |
Open-Jev: typed decision datasets
Open-Jev turns a state and a question into a typed decision: a yes/no probability, a distribution over choices, independent label probabilities, or a discrete numeric/ordinal decision. This repository publishes twelve separate, frozen data configs from the Open-Jev project, together with original manifests, exact raw records, source code and reconstruction instructions.
These are controlled, mostly synthetic tasks and reference labels. They are not official TypeSafe/Jev training data, model predictions, or evidence of general capability. Open-Jev is independently implemented and is not affiliated with TypeSafe.
Configs and exact split counts
| Config | Train | Calibration | Validation | Test | OOD | Total |
|---|---|---|---|---|---|---|
release-v2-redistributable |
79,116 | 4,672 | 3,723 | 10,356 | 15,701 | 113,568 |
browser-drone-expansion-v1-redistributable |
108,624 | 6,794 | 5,493 | 14,726 | 25,160 | 160,797 |
citation-control-v1 |
2,520 | 200 | 180 | 300 | 800 | 4,000 |
entity-alignment-control-v1 |
6,944 | 728 | 280 | 1,008 | 2,240 | 11,200 |
amount-extraction-control-v1 |
32,984 | 2,232 | 992 | 3,472 | 9,920 | 49,600 |
email-selection-control-v1 |
3,618 | 81 | 189 | 432 | 1,080 | 5,400 |
phone-extraction-control-v1 |
12,350 | 855 | 380 | 1,615 | 3,800 | 19,000 |
context-retention-control-v1 |
6,138 | 456 | 558 | 522 | 2,160 | 9,834 |
sponsor-segment-control-v1 |
6,345 | 756 | 540 | 999 | 2,160 | 10,800 |
silent-failure-control-v1 |
6,432 | 264 | 360 | 624 | 1,920 | 9,600 |
ir-control-v1 |
7,366 | 464 | 464 | 986 | 2,320 | 11,600 |
mailroom-control-v1 |
73,472 | 4,018 | 6,027 | 8,323 | 22,960 | 114,800 |
The configs overlap. release-v2-redistributable is contained in browser-drone-expansion-v1-redistributable; do not add config totals and call them unique examples. Counts are typed decision rows. Several heads may come from the same conversation, document, family or game trajectory.
The original frozen release-v2 used to train the 2B/9B models has 80,816 training rows and 115,821 rows across all splits. The public projection above is not that exact training dataset. Each of the two composite configs excludes exactly 2,253 Wikispeedia rows: 1,700 train, 89 calibration, 69 validation, 176 test and 219 OOD. The original expansion mixture has 163,050 rows, including 110,324 train. Original manifests and hashes are preserved without modification; REPRODUCTION.md explains how to restore both exact original mixtures with separately obtained source data.
The five citation/entity/amount/email/phone corpora were prepared and audited after those 2B/9B runs. They have not been used for training or actual model inference at the time of this release. The expansion mixture belongs to a separate 27B experiment; this dataset publication makes no completed-training or performance claim for that experiment.
Load and decode
import json
from datasets import load_dataset
ds = load_dataset("ZefanCai/Open-Jev", "release-v2-redistributable")
example = ds["train"][0]
state = json.loads(example["state_json"])
metadata = json.loads(example["metadata_json"])
original_record = json.loads(example["record_json"])
For reproducibility, pass revision="<dataset commit SHA>". Choose a config explicitly; loading the default does not include the separate control corpora.
| Column | Meaning |
|---|---|
id, group_id, split, source |
Original identity, grouping, split and generator/source version. |
kind |
Original decision type; interpret with the source task definition. |
question, options |
Model-visible question and ordered answer space. |
target |
Original numeric reference targets, represented as a float64 list. These are labels, not measured model confidence. |
state_json |
JSON encoding of the original state. Decoding returns a string or structured object, depending on the source. |
metadata_json |
Original provenance and audit metadata. It can include privileged teacher/control labels and must not be used as model input. |
record_json |
Complete original JSON record, retaining original object key order and numeric representation. |
original_line_number |
One-based row position in the original frozen split, including positions of excluded rows. |
The Parquet representation avoids imposing one nested schema on different task states. raw/<config>/<split>.jsonl.gz preserves the source JSONL bytes after decompression. For the filtered composites, retained lines preserve exact bytes and order. For the ten stand-alone control configs, decompressed files match the original frozen split hashes exactly.
Use only state, question, kind and options as model inputs. Do not expose target, metadata, identities, split assignments or provenance fields to the model. Distribution, binary, multilabel and ordinal targets have different semantics; do not reduce every row to a single-class accuracy calculation.
Domains and construction
- The base release covers controlled customer-support routing and triage; local workflow decisions; geometric painting probability requests; Snake and tic-tac-toe; simplified T-Rex/runner and platformer controls; numeric ViZDoom Basic trajectories; and controlled reasoning decisions.
- The expansion additionally includes controlled browser state/action and drone state/control examples. These represent the declared simulated task forms, not unrestricted browser use or real aircraft operation.
- Citation data uses original policy documents, quotes, visible facts and claims, with supported/contradicted/insufficient decisions. It tests those controlled relations, not arbitrary factual verification.
- Entity alignment uses original catalog families, records, aliases and visible matching policies with multiple decision heads.
- Amount, email and phone extraction separate deterministic candidate generation from typed selection/attribute decisions. Known candidate misses and partial matches are retained rather than replaced using gold answers. Conditional attribute heads and omitted-supervision counts are documented in the original manifests.
The new corpora include compressed documents/families/cases in artifacts/. These are reproduction/audit artifacts, not additional typed rows to add to the totals. Citation has 200 documents and 4,400 cases: 4,000 typed semantic cases plus 400 quote-not-found controls. Entity alignment has 200 families and 2,800 cases; amount has 200 families and 3,200 documents; email has 200 families and 2,800 documents; phone has 200 families and 4,000 documents.
Original data and split policies are recorded per corpus in provenance/original-manifests/. Related documents/entities/trajectories remain grouped within splits. OOD is source-specific, commonly reserved wording, layouts, control families or goals, and is not a universal unseen-domain benchmark. Local export verification checks unique IDs and cross-split group separation within each config.
Evaluation boundaries
Train, calibration, validation, test and OOD are published separately. Train on the train split; use calibration only for the declared calibration procedure and validation for model selection. Test/OOD labels are public, so future work must disclose any use of them for development. Scores measured on the original full frozen mixtures must not be described as scores on these smaller public projections without recomputation.
No Jev Frontier 100 question/answer payload is included. The external jev-frontier-100 benchmark remains separate from training and generation. No official private examples, game ROMs, game assets, model weights or credentials are included.
Licensing and provenance
Original generated records are marked CC0-1.0 in their existing provenance. This dedication covers our generated content, not upstream wording, external assets, source data or model weights. Original source code is MIT. Customer-control provenance retains its original note that short upstream question descriptions come from TypeSafe documentation without a verified source license; this release does not relicense those descriptions. See THIRD_PARTY_NOTICES.md.
The Wikispeedia archive does not declare a verified separate graph/path redistribution license. Therefore its task rows are excluded from the two public mixture projections. We do not infer that a current Wikipedia license covers the archived graph/path dataset. We publish its original manifest, source URL, archive SHA-256, exact exclusion positions and a local reconstruction utility, not its graph, paths or task payload.
Wikispeedia references:
- West and Leskovec. Human Wayfinding in Information Networks. WWW 2012.
- West, Pineau and Precup. Wikispeedia: An Online Game for Inferring Semantic Distances between Concepts. IJCAI 2009.
export-manifest.json records original and public split counts/hashes, source counts, exclusion positions, source-code fingerprints and published file hashes. REPRODUCTION.md documents exact restoration and generator commands. The dataset repository's Git commit pins this complete release.
Community task additions — 2026-09-20
Three additional original CC0 control configs contribute 30,234 typed rows across 15 new splits. That addition brought the repository to 10 configs and 50 splits. Existing configs, payloads, manifests and the default remain unchanged.
These three additions have not been used for training or model evaluation. Independent data audits validate their reference labels and split integrity; they are not model benchmarks. The released 2B/9B training mixture is unchanged.
context-retention-control-v1: Keep or discard eligible completed tool-call records and full outputs under an explicit fixed retention policy. The shared state contains context, goal and history; full tool outputs are omitted. Two Noul questions are built per eligible call. Labels follow visible goal dependency closure, exact-evidence needs and output recoverability. Pinned and pending calls are software gates, without model labels. Whole task graphs and their goal/recoverability counterfactuals share a split. OOD reserves diamond dependencies and wording. This finite synthetic task is not evidence of useful arbitrary-session compaction.sponsor-segment-control-v1: Categorize original timestamped transcript segments with one Choice per segment: sponsor, self_promo, intro, outro, recap, content or other. Paid third-party promotion needs affirmative funding evidence; creator-owned promotion is separate. A brand, discount code or promo marker alone does not establish sponsorship. Complete video families and payment-evidence counterfactuals share a split; OOD reserves complete sentence wording. The data are finite synthetic transcripts, not scraped videos or an audio/visual benchmark.silent-failure-control-v1: Ask one is_silent_failure Noul using only the exact response body string. The transport status is outside model input. Current maintenance, business rejection, a sign-in page replacing requested data, missing explicitly required receipts and unmet delivery requirements are contrasted with valid empty results, recovered history, quoted error text, accepted queued jobs and permitted partial results. Judge transport failures never become negative ground truth. Whole provider/contract families retain all counterfactuals; OOD reserves Chinese wording and different JSON/HTML/text layouts. This controlled grammar does not establish correctness for arbitrary APIs.
The new original cases remain separate audit artifacts. Exact raw JSONL bytes, original manifests and an isolated source snapshot accompany the Parquet splits. The additive export manifest records only these additions; the original export-manifest.json is retained byte for byte.
Original retrieval-control addition — 2026-09-20
ir-control-v1 adds 11,600 typed rows across five
splits, representing 8,800 requests, 400 queries and 200 complete fictional
system families. That addition brought the repository to 11 configs and 55 splits.
It supports pointwise Noul/Score, pairwise/setwise Choice and listwise
Choice/Score task forms under an original four-level relevance rubric.
Choice labels supervise best-passage selection, not full ranking or uncertainty.
The full corpus passed an independent body-derived label audit. No training on these IR records is claimed. A separately frozen six-query Jev pilot is documented in the source project; it is not a full-corpus or TREC evaluation. No TREC data, qrels, provider responses or third-party examples are included. Frozen pilot test/OOD families remain held out in the expanded corpus.
All existing dataset payloads, original manifests, config definitions, the default config and frozen model-training mixtures remain unchanged. The IR export manifest binds this addition only.
Original multilingual mailroom addition — 2026-09-20
mailroom-control-v1 adds 114,800 typed rows
across five splits, from 11,600 original email requests and 400 complete
English/Chinese/Turkish families. The repository now declares 12 configs and
60 splits. Each request retains the source-shaped two Choice and nine Noul
questions. Nonbill/nonreceipt categories have no supervised label, and unchanged
heads across taxonomy variants share their original row. There are 114,800
unique ordered inputs, or 114,400 after also disregarding candidate order.
The independent auditor derives labels from final visible email text and taxonomy. All frozen probe rows/cases keep their bytes and split assignments. No real mailbox contents, private source examples, attachments or provider responses are included. No training or full-corpus model evaluation is claimed; the separately documented 87-request Jev probe is not production mail-triage accuracy or end-to-end mailbox automation.
All existing payloads, manifests, config definitions, the default config and frozen training mixtures remain unchanged, including the preceding IR addition. The mailroom export manifest binds only this new config and its auxiliary audit artifacts.
- Downloads last month
- 167