Dataset Viewer
Auto-converted to Parquet Duplicate
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
End of preview. Expand in Data Studio

ZefanCai/Open-Jev๏ผˆ่ค‡่ฃฝ๏ผ‰

ใƒ‡ใƒผใ‚ฟใฎๅ†…ๅฎน

ๅคงๅŠใŒๅˆๆˆใฎใ‚ฟใ‚นใ‚ฏใจๅ‚็…งใƒฉใƒ™ใƒซใ‹ใ‚‰ใชใ‚‹ๅž‹ไป˜ใใฎๅˆคๆ–ญใฎใƒ‡ใƒผใ‚ฟใ€‚1 ่กŒใŒ 1 ไปถใฎๅˆคๆ–ญใงใ€questionใƒปoptionsใƒปtarget๏ผˆใƒฉใƒ™ใƒซใฎๅˆ†ๅธƒ๏ผ‰ใจใ€ๅ…ƒใฎ็Šถๆ…‹ใ‚’ JSON ใซใ—ใŸ state_json ใชใฉใ‹ใ‚‰ใชใ‚‹ใ€‚TypeSafe ใฎๅ…ฌๅผใฎ Jev ใƒ‡ใƒผใ‚ฟใงใ‚‚ใ€ใƒขใƒ‡ใƒซใฎไบˆๆธฌใงใ‚‚ใชใ„ใ€‚config ใฉใ†ใ—ใฏ้‡ใชใ‚‹ใŸใ‚ใ€ไปถๆ•ฐใ‚’่ถณใ—ใฆไธ€ๆ„ใฎไพ‹ใจใฟใชใ—ใฆใฏใชใ‚‰ใชใ„ใ€‚

ใƒ‡ใƒผใ‚ฟใฎๆฆ‚่ฆ

้ …็›ฎ ๅ€ค
่กŒๆ•ฐ 520,199๏ผˆ12 ๆง‹ๆˆใƒป60 ๅˆ†ๅ‰ฒใฎๅˆ่จˆ๏ผ‰
ๅˆ—ๆ•ฐ 12
ๅฎน้‡ 86.77 MB๏ผˆใƒ•ใ‚กใ‚คใƒซ 236 ๆœฌ๏ผ‰
ใƒ•ใ‚กใ‚คใƒซใฎๅฝขๅผ jsonl.gz 79ใ€parquet 60ใ€json 35ใ€py 12ใ€md 7ใ€๏ผˆๆ‹กๅผตๅญใชใ—๏ผ‰ 2
่จ€่ชž en, zh, tr
ๅ…ฌ้–‹ public

ๆง‹ๆˆใจๅˆ†ๅ‰ฒ

ๆง‹ๆˆ๏ผˆconfig๏ผ‰ ๅˆ†ๅ‰ฒ๏ผˆsplit๏ผ‰ใ”ใจใฎ่กŒๆ•ฐ ๅˆ—ๆ•ฐ
release-v2-redistributable train 79,116ใ€calibration 4,672ใ€validation 3,723ใ€test 10,356ใ€ood 15,701 12
amount-extraction-control-v1 train 32,984ใ€calibration 2,232ใ€validation 992ใ€test 3,472ใ€ood 9,920 12
browser-drone-expansion-v1-redistributable train 108,624ใ€calibration 6,794ใ€validation 5,493ใ€test 14,726ใ€ood 25,160 12
citation-control-v1 train 2,520ใ€calibration 200ใ€validation 180ใ€test 300ใ€ood 800 12
context-retention-control-v1 train 6,138ใ€calibration 456ใ€validation 558ใ€test 522ใ€ood 2,160 12
email-selection-control-v1 train 3,618ใ€calibration 81ใ€validation 189ใ€test 432ใ€ood 1,080 12
entity-alignment-control-v1 train 6,944ใ€calibration 728ใ€validation 280ใ€test 1,008ใ€ood 2,240 12
ir-control-v1 train 7,366ใ€calibration 464ใ€validation 464ใ€test 986ใ€ood 2,320 12
mailroom-control-v1 train 73,472ใ€calibration 4,018ใ€validation 6,027ใ€test 8,323ใ€ood 22,960 12
phone-extraction-control-v1 train 12,350ใ€calibration 855ใ€validation 380ใ€test 1,615ใ€ood 3,800 12
silent-failure-control-v1 train 6,432ใ€calibration 264ใ€validation 360ใ€test 624ใ€ood 1,920 12
sponsor-segment-control-v1 train 6,345ใ€calibration 756ใ€validation 540ใ€test 999ใ€ood 2,160 12

ๅˆ—๏ผˆๆง‹ๆˆ release-v2-redistributableใƒปๅˆ†ๅ‰ฒ trainใ€‚ใฉใฎๆง‹ๆˆใ‚‚ๅŒใ˜ๅˆ—๏ผ‰

ๅˆ— ๅž‹ ๅ…ˆ้ ญใฎ่กŒใฎๅ€ค
id string customer-control-v1:42:1:category
group_id string customer-control-v1:42:1
split string train
source string customer-control-v1
kind string choice
question string Determine the broad category of this support ticโ€ฆ
options list<string> [4 ไปถ]
target list<float64> [4 ไปถ]
state_json string "Conversation with account holder Harbor-65673baโ€ฆ
metadata_json string {"case_name": "customer_support_fanout_control",โ€ฆ
record_json string {"group_id": "customer-control-v1:42:1", "id": "โ€ฆ
original_line_number int64 1

่กŒๆ•ฐใจๅˆ—ใฏ HF ใฎใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใƒ“ใƒฅใƒผใ‚ขใฎ้›†่จˆ๏ผˆๅ…ƒใฎใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใฎ็พๅœจใฎ็‰ˆใงๆ•ฐใˆใŸใ‚‚ใฎ๏ผ‰ใ€‚ๅ…จใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใฎไธ€่ฆงใฏ HYUKI5/dataset-catalog ใซใ‚ใ‚‹ใ€‚

่ค‡่ฃฝใซใคใ„ใฆ

ZefanCai/Open-Jev ใ‚’ใƒชใƒ“ใ‚ธใƒงใƒณ c67699e13d0ae25e35b77165a4b6b079bedc8aba ใฎๆ™‚็‚นใงใใฎใพใพ่ค‡่ฃฝใ—ใŸใ‚‚ใฎใ€‚ไธญ่บซใฏๅค‰ใˆใฆใ„ใชใ„ใ€‚ๅˆคๆ–ญใƒขใƒ‡ใƒซ Laya๏ผˆconvaiinnovations/laya๏ผ‰ใฎๅพฎ่ชฟๆ•ดใซไฝฟใ†ๅ€™่ฃœใจใ—ใฆใ€่ชฟๆŸปใƒกใƒข๏ผˆLaya ๅญฆ็ฟ’็”จใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆ่ชฟๆŸป๏ผ‰ใซ่ผ‰ใ›ใŸใƒ‡ใƒผใ‚ฟใ‚’้›†ใ‚ใฆใ„ใ‚‹ใ€‚

ๅ‡บๅ…ธ

  • ๅ…ƒใฎใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆ: https://huggingface.co/datasets/ZefanCai/Open-Jev
  • ่ค‡่ฃฝใ—ใŸใƒชใƒ“ใ‚ธใƒงใƒณ: c67699e13d0ae25e35b77165a4b6b079bedc8aba๏ผˆ2026-09-20 22:49:59+00:00๏ผ‰
  • ๅ…ƒใฎใƒฉใ‚คใ‚ปใƒณใ‚น่กจ่จ˜: cc0-1.0

่ซ–ๆ–‡

  • ๅ…ƒใฎใ‚ซใƒผใƒ‰ใซ่ซ–ๆ–‡ใธใฎใƒชใƒณใ‚ฏใฏ่ฆ‹ใคใ‹ใ‚‰ใชใ‹ใฃใŸ

ใ‚ขใƒŽใƒ†ใƒผใ‚ทใƒงใƒณใฎๆ–นๆณ•

้ ˜ๅŸŸใจๆง‹็ฏ‰

  • ๅŸบๆœฌใฎใƒชใƒชใƒผใ‚นใฏใ€็ตฑๅˆถใ•ใ‚ŒใŸ้กงๅฎขใ‚ตใƒใƒผใƒˆใฎใƒซใƒผใƒ†ใ‚ฃใƒณใ‚ฐใจใƒˆใƒชใ‚ขใƒผใ‚ธใ€ใƒญใƒผใ‚ซใƒซใชใƒฏใƒผใ‚ฏใƒ•ใƒญใƒผใฎๅˆคๆ–ญใ€ๅนพไฝ•ๅญฆ็š„ใช็ตต็”ปใฎ็ขบ็އใฎ่ฆๆฑ‚ใ€Snake ใจไธ‰็›ฎไธฆในใ€็ฐก็•ฅๅŒ–ใ•ใ‚ŒใŸ T-Rex/runner ใจใƒ—ใƒฉใƒƒใƒˆใƒ•ใ‚ฉใƒผใƒžใƒผใฎๆ“ไฝœใ€ๆ•ฐๅ€คใฎ ViZDoom Basic ใฎ่ปŒ่ทกใ€็ตฑๅˆถใ•ใ‚ŒใŸๆŽจ่ซ–ใฎๅˆคๆ–ญใ‚’ๆ‰ฑใ†ใ€‚
  • expansion ใซใฏใ€็ตฑๅˆถใ•ใ‚ŒใŸใƒ–ใƒฉใ‚ฆใ‚ถใฎ็Šถๆ…‹ใƒปๆ“ไฝœใจใ€ใƒ‰ใƒญใƒผใƒณใฎ็Šถๆ…‹ใƒปๅˆถๅพกใฎไพ‹ใŒใ•ใ‚‰ใซๅซใพใ‚Œใ‚‹ใ€‚ใ“ใ‚Œใ‚‰ใฏๅฎฃ่จ€ใ•ใ‚ŒใŸใ‚ทใƒŸใƒฅใƒฌใƒผใ‚ทใƒงใƒณใฎใ‚ฟใ‚นใ‚ฏๅฝขๅผใ‚’่กจใ™ใ‚‚ใฎใงใ‚ใ‚Šใ€ๅˆถ้™ใฎใชใ„ใƒ–ใƒฉใ‚ฆใ‚ถใฎๅˆฉ็”จใ‚„ๅฎŸๆฉŸใฎ่ˆช็ฉบๆฉŸใฎๆ“็ธฆใงใฏใชใ„ใ€‚
  • citation ใฎใƒ‡ใƒผใ‚ฟใฏใ€ๅ…ƒใฎๆ–น้‡ๆ–‡ๆ›ธใ€ๅผ•็”จใ€่ฆ‹ใˆใ‚‹ไบ‹ๅฎŸใจไธปๅผตใ‚’ไฝฟใ„ใ€supported/contradicted/insufficient ใฎๅˆคๆ–ญใ‚’ไป˜ใ‘ใ‚‹ใ€‚่ฉฆใ•ใ‚Œใ‚‹ใฎใฏ็ตฑๅˆถใ•ใ‚ŒใŸ้–ขไฟ‚ใงใ‚ใ‚Šใ€ไปปๆ„ใฎไบ‹ๅฎŸ็ขบ่ชใงใฏใชใ„ใ€‚
  • entity alignment ใฏใ€ๅ…ƒใฎใ‚ซใ‚ฟใƒญใ‚ฐใฎใƒ•ใ‚กใƒŸใƒชใƒผใ€ใƒฌใ‚ณใƒผใƒ‰ใ€ๅˆฅๅใ€่ฆ‹ใˆใ‚‹็…งๅˆๆ–น้‡ใ‚’ใ€่ค‡ๆ•ฐใฎๅˆคๆ–ญใƒ˜ใƒƒใƒ‰ใจใจใ‚‚ใซไฝฟใ†ใ€‚
  • amountใƒปemailใƒปphone ใฎๆŠฝๅ‡บใฏใ€ๆฑบๅฎš็š„ใชๅ€™่ฃœ็”Ÿๆˆใ‚’ๅž‹ไป˜ใใฎ้ธๆŠžใƒปๅฑžๆ€งใฎๅˆคๆ–ญใ‹ใ‚‰ๅˆ†ใ‘ใฆใ„ใ‚‹ใ€‚ๆ—ข็Ÿฅใฎๅ€™่ฃœใฎๅ–ใ‚Š้€ƒใŒใ—ใจ้ƒจๅˆ†ไธ€่‡ดใฏใ€ๆญฃ่งฃ๏ผˆgold answer๏ผ‰ใ‚’ไฝฟใฃใฆ็ฝฎใๆ›ใˆใšไฟๆŒใ•ใ‚Œใ‚‹ใ€‚ๆกไปถไป˜ใใฎๅฑžๆ€งใƒ˜ใƒƒใƒ‰ใจใ€็œใ‹ใ‚ŒใŸๆ•™ๅธซใฎไปถๆ•ฐใฏๅ…ƒใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใซ่จ˜้Œฒใ•ใ‚Œใฆใ„ใ‚‹ใ€‚

ๆ–ฐใ—ใ„ใ‚ณใƒผใƒ‘ใ‚นใฏใ€artifacts/ ใซๅœง็ธฎใ•ใ‚ŒใŸๆ–‡ๆ›ธใƒปใƒ•ใ‚กใƒŸใƒชใƒผใƒปใ‚ฑใƒผใ‚นใ‚’ๅซใ‚€ใ€‚ใ“ใ‚Œใ‚‰ใฏๅ†็พใจ็›ฃๆŸปใฎใŸใ‚ใฎๆˆๆžœ็‰ฉใงใ‚ใ‚Šใ€ๅˆ่จˆใซๅŠ ใˆใ‚‹ๅž‹ไป˜ใใฎ่กŒใงใฏใชใ„ใ€‚citation ใฏ 200 ๆ–‡ๆ›ธใจ 4,400 ใ‚ฑใƒผใ‚นใ‚’ๆŒใคใ€‚ๅ†…่จณใฏใ€4,000 ใฎๅž‹ไป˜ใใฎๆ„ๅ‘ณใ‚ฑใƒผใ‚นใจใ€400 ใฎใ€Œๅผ•็”จใŒ่ฆ‹ใคใ‹ใ‚‰ใชใ„ใ€็ตฑๅˆถใ‚ฑใƒผใ‚นใ€‚entity alignment ใฏ 200 ใƒ•ใ‚กใƒŸใƒชใƒผใจ 2,800 ใ‚ฑใƒผใ‚นใ€amount ใฏ 200 ใƒ•ใ‚กใƒŸใƒชใƒผใจ 3,200 ๆ–‡ๆ›ธใ€email ใฏ 200 ใƒ•ใ‚กใƒŸใƒชใƒผใจ 2,800 ๆ–‡ๆ›ธใ€phone ใฏ 200 ใƒ•ใ‚กใƒŸใƒชใƒผใจ 4,000 ๆ–‡ๆ›ธใ‚’ๆŒใคใ€‚

ๅ…ƒใฎใƒ‡ใƒผใ‚ฟใจๅˆ†ๅ‰ฒใฎๆ–น้‡ใฏใ€ใ‚ณใƒผใƒ‘ใ‚นใ”ใจใซ provenance/original-manifests/ ใซ่จ˜้Œฒใ•ใ‚Œใฆใ„ใ‚‹ใ€‚้–ข้€ฃใ™ใ‚‹ๆ–‡ๆ›ธใƒปใ‚จใƒณใƒ†ใ‚ฃใƒ†ใ‚ฃใƒป่ปŒ่ทกใฏใ€ๅˆ†ๅ‰ฒใฎไธญใงใ‚ฐใƒซใƒผใƒ—ๅŒ–ใ•ใ‚ŒใŸใพใพๆฎ‹ใ‚‹ใ€‚OOD ใฏใ‚ฝใƒผใ‚นใ”ใจใฎใ‚‚ใฎใงใ€ใ‚ˆใไบˆ็ด„ใ•ใ‚ŒใŸ่จ€ใ„ๅ›žใ—ใ€ใƒฌใ‚คใ‚ขใ‚ฆใƒˆใ€ๅˆถๅพกใฎใƒ•ใ‚กใƒŸใƒชใƒผใ‚„็›ฎๆจ™ใงใ‚ใ‚Šใ€ๆ™ฎ้็š„ใชๆœช็Ÿฅ้ ˜ๅŸŸใฎใƒ™ใƒณใƒใƒžใƒผใ‚ฏใงใฏใชใ„ใ€‚ใƒญใƒผใ‚ซใƒซใฎใ‚จใ‚ฏใ‚นใƒใƒผใƒˆๆคœ่จผใฏใ€config ใ”ใจใซ ID ใฎไธ€ๆ„ๆ€งใจใ€ๅˆ†ๅ‰ฒใ‚’ใพใŸใใ‚ฐใƒซใƒผใƒ—ใฎๅˆ†้›ขใ‚’็ขบใ‹ใ‚ใ‚‹ใ€‚

ๅพฎ่ชฟๆ•ดใซไฝฟใ†ใจใใฎๆณจๆ„

  • ่ชฟๆŸปใƒกใƒขใฎๅฐๅธณใงใฎๅŒบๅˆ†: D๏ผˆ่จ˜่ผ‰ใชใ—ใƒปotherใƒปunknownใƒป่ณ‡ๆ–™้–“ใฎ้ฃŸใ„้•ใ„๏ผ‰ใ€‚ๅŒบๅˆ†ใฏ่จ˜่ผ‰ใฎๆ–‡่จ€ใงๆฉŸๆขฐ็š„ใซไป˜ใ‘ใŸใ‚‚ใฎใงใ€ๆณ•็š„ใชๅˆคๅฎšใงใฏใชใ„ใ€‚ๅญฆ็ฟ’ใซๅ…ฅใ‚Œใ‚‹ๅ‰ใซๅ…ƒใฎใ‚ซใƒผใƒ‰ใจใƒฉใ‚คใ‚ปใƒณใ‚นใฎๅŽŸๆ–‡ใง็ขบใ‹ใ‚ใ‚‹ใ€‚
  • Laya ใฎๅ…ฅๅŠ›ใฏ 2,048 token ใพใง๏ผˆModernBERT-large / mmBERT๏ผ‰ใ€‚้•ทใ„ๆœฌๆ–‡ใฏๅ…ˆ้ ญใ‹ใ‚‰้ป™ใฃใฆๅˆ‡ใ‚‰ใ‚Œใ‚‹ใฎใงใ€ๅˆ‡ใ‚Œใ‚‹่กŒใฏไบ‹ๅ‰ใซ้™คใใ‹ใ€่ฆ็ด„ใƒปๅˆ‡ใ‚Šๅ‡บใ—ใ‚’ใ—ใฆใ‹ใ‚‰ๅ…ฅใ‚Œใ‚‹ใ€‚
  • ๅˆ†ๅ‰ฒใฏ่จ˜ไบ‹ใƒปๆ–‡ๆ›ธๅ˜ไฝใง่กŒใ„ใ€ๅŒใ˜ๆœฌๆ–‡ใ‹ใ‚‰ไฝœใฃใŸๅˆฅใฎๅ•ใ„ใ‚’ๅญฆ็ฟ’ๅดใจ่ผƒๆญฃๅดใซๅˆ†ใ‘ใชใ„ใ€‚ๆธฉๅบฆใจ้–พๅ€คใฏๅญฆ็ฟ’ใซไฝฟใฃใฆใ„ใชใ„ๅˆ†ๅ‰ฒใงๅˆฅใ€…ใซๅฝ“ใฆใ‚‹ใ€‚

่ฉ•ไพกใƒ‡ใƒผใ‚ฟใฎๆททๅ…ฅ๏ผˆๆœฌๆ–‡็…งๅˆใฎ็ตๆžœ๏ผ‰

ๅ…ƒใฎ source / config ๆททๅ…ฅใ—ใŸ่ฉ•ไพกใ‚ปใƒƒใƒˆ split ็…งๅˆ ไปถๆ•ฐ ่ฉ•ไพกใ‚ปใƒƒใƒˆใฎไปถๆ•ฐ ๆŽจๅฅจใฎๅ‡ฆ็ฝฎ
all configs@train ag_news test none 0 7600 no_action
all configs@train banking77 test none 0 3080 no_action
all configs@train boolq validation none 0 3270 no_action
all configs@train localllama_typed test none 0 400 no_action
all configs@train massive_en test none 0 2974 no_action
all configs@train sst5 test none 0 2210 no_action
all configs@train xnli_en test none 0 5010 no_action

่ชฟๆŸปใƒกใƒขใฎ่จ˜่ฟฐ

ใƒกใƒข ็ฏ€ ใƒฉใ‚คใ‚ปใƒณใ‚น๏ผˆ่จ˜่ผ‰๏ผ‰ ็ขบ่ช ๆณจ่จ˜
multitask_weak_synthetic.md Q1. Laya ใจๅŒๅฝขๅผใฎๅˆๆˆใƒปๅค‰ๆ›ๆธˆใฟใ€Œtyped decisionsใ€ใƒ‡ใƒผใ‚ฟใฏใ€ๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใ‚‹ใ‹ (L27) ็”Ÿๆˆใƒฌใ‚ณใƒผใƒ‰ CC0-1.0ใ€ใ‚ณใƒผใƒ‰ MITใ€‚ไธŠๆตใฎ่ชฌๆ˜Žๆ–‡ใƒปWikispeedia ใชใฉใฏๅˆฅๆ‰ฑใ„ใ€‚HF API ใฏ cc0-1.0 ็ขบ่ชๆธˆ ่ค‡ๆ•ฐ/ๆททๅœจ/ไธŠๆต/ๆกไปถๆณจ่จ˜ ๏ผ ๅŽŸๆ–‡ๆณจ่จ˜: ๅˆๆˆใงใƒ†ใƒณใƒ—ใƒฌใƒผใƒˆ็š„ใ€‚Wikispeedia ใฏๅ†้…ๅธƒใƒฉใ‚คใ‚ปใƒณใ‚นใŒไธๆ˜ŽใฎใŸใ‚้™คๅค–ๆธˆใฟใ€‚customer-control ใฎ่ณชๅ•ๆ–‡ใฏ TypeSafe ใฎใƒ‰ใ‚ญใƒฅใƒกใƒณใƒˆ็”ฑๆฅใงใƒฉใ‚คใ‚ปใƒณใ‚นๆœชๆคœ่จผ๏ผˆREADME๏ผ‰ใ€‚metadata
reasoning_argument_numeric.md Q8. Laya ใจๅŒใ˜ typed-decisions ใฎๅฝข๏ผˆnoul / choice / score + ็ขบ็އๅˆ†ๅธƒ๏ผ‰ใซๆ•ดๅฝขๆธˆใฟใฎๅ…ฌ้–‹ใƒ‡ใƒผใ‚ฟใฏใ‚ใ‚‹ใ‹ (L214) cc0-1.0 ็ขบ่ชๆธˆ ๅŽŸๆ–‡ๆณจ่จ˜: ใ‚จใƒผใ‚ธใ‚งใƒณใƒˆๅˆถๅพก็”จใฎๅˆๆˆใƒ‡ใƒผใ‚ฟใงใ€้‡‘่žใฎ่ซ–่จผใจใฏ้ ใ„ใ€‚ไปถๆ•ฐใƒปๅ†…ๅฎนใฏๆœชๅ–ๅพ—
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0 (conversations); question license unknown ็ขบ่ชๆธˆ ่ค‡ๆ•ฐ/ๆททๅœจ ๏ผ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti
jev_sources_tasksource_bekko.csv CSV๏ผˆbekko-system-one-dataset-v0๏ผ‰ CC0-1.0 ็ขบ่ชๆธˆ [Jev ๅ…ƒใƒ‡ใƒผใ‚ฟ source] synthetic_reference_labels(Open-Jev; rule/policy teacher; ti

ๅ…ƒใฎใ‚ซใƒผใƒ‰๏ผˆๆ—ฅๆœฌ่ชž่จณ๏ผ‰

ไปฅไธ‹ใฏๅ…ƒใฎใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใฎใ‚ซใƒผใƒ‰ใฎๆœฌๆ–‡ใ‚’ๆ—ฅๆœฌ่ชžใซ่จณใ—ใŸใ‚‚ใฎ๏ผˆๆฉŸๆขฐ็ฟป่จณ๏ผ‰ใ€‚่จณใซ็–‘ๅ•ใŒใ‚ใ‚‹ใจใใฏใ€ๆœซๅฐพใฎๅŽŸๆ–‡ใ‚’็ขบใ‹ใ‚ใ‚‹ใ€‚


Open-Jev: ๅž‹ไป˜ใใฎๅˆคๆ–ญใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆ

Open-Jev ใฏใ€็Šถๆ…‹ใจ่ณชๅ•ใ‚’ๅž‹ไป˜ใใฎๅˆคๆ–ญใซๅค‰ใˆใ‚‹ใ€‚ๅˆคๆ–ญใฏใ€yes/no ใฎ็ขบ็އใ€้ธๆŠž่‚ขไธŠใฎๅˆ†ๅธƒใ€็‹ฌ็ซ‹ใ—ใŸใƒฉใƒ™ใƒซใ”ใจใฎ็ขบ็އใ€้›ขๆ•ฃ็š„ใชๆ•ฐๅ€คใƒป้ †ๅบใฎๅˆคๆ–ญใฎใ„ใšใ‚Œใ‹ใงใ‚ใ‚‹ใ€‚ใ“ใฎใƒชใƒใ‚ธใƒˆใƒชใฏใ€Open-Jev ใƒ—ใƒญใ‚ธใ‚งใ‚ฏใƒˆ ใ‹ใ‚‰ๆดพ็”Ÿใ—ใŸ 12 ๅ€‹ใฎๅˆฅใ€…ใฎๅ‡็ตใ•ใ‚ŒใŸใƒ‡ใƒผใ‚ฟ config ใ‚’ใ€ๅ…ƒใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใ€ๅŽŸๆ–‡ใฉใŠใ‚Šใฎ็”Ÿใƒฌใ‚ณใƒผใƒ‰ใ€ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใ€ๅ†ๆง‹ๆˆใฎๆ‰‹้ †ใจใจใ‚‚ใซๅ…ฌ้–‹ใ™ใ‚‹ใ€‚

ใ“ใ‚Œใ‚‰ใฏ็ตฑๅˆถใ•ใ‚ŒใŸใ€ๅคงๅŠใŒๅˆๆˆใฎใ‚ฟใ‚นใ‚ฏใจๅ‚็…งใƒฉใƒ™ใƒซใงใ‚ใ‚‹ใ€‚TypeSafe/Jev ใฎๅ…ฌๅผใชๅญฆ็ฟ’ใƒ‡ใƒผใ‚ฟใ€ใƒขใƒ‡ใƒซใฎไบˆๆธฌใ€ๆฑŽ็”จ็š„ใช่ƒฝๅŠ›ใฎ่จผๆ‹ ใงใฏใชใ„ใ€‚Open-Jev ใฏ็‹ฌ็ซ‹ใซๅฎŸ่ฃ…ใ•ใ‚ŒใŸใ‚‚ใฎใงใ€TypeSafe ใจใฏๆๆบใ—ใฆใ„ใชใ„ใ€‚

config ใจๅˆ†ๅ‰ฒใ”ใจใฎๆญฃ็ขบใชไปถๆ•ฐ

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

config ใฏ้‡ใชใ‚‹ใ€‚ release-v2-redistributable ใฏ browser-drone-expansion-v1-redistributable ใซๅซใพใ‚Œใ‚‹ใ€‚config ใฎๅˆ่จˆใ‚’่ถณใ—ใฆไธ€ๆ„ใฎไพ‹ใจๅ‘ผใ‚“ใงใฏใชใ‚‰ใชใ„ใ€‚ไปถๆ•ฐใฏๅž‹ไป˜ใใฎๅˆคๆ–ญใฎ่กŒๆ•ฐใงใ‚ใ‚‹ใ€‚ใ„ใใคใ‹ใฎใƒ˜ใƒƒใƒ‰๏ผˆhead๏ผ‰ใฏใ€ๅŒใ˜ไผš่ฉฑใƒปๆ–‡ๆ›ธใƒปใƒ•ใ‚กใƒŸใƒชใƒผใƒปใ‚ฒใƒผใƒ ใฎ่ปŒ่ทกใ‹ใ‚‰ๆฅใ‚‹ใ“ใจใŒใ‚ใ‚‹ใ€‚

ๅ…ƒใฎๅ‡็ตใ•ใ‚ŒใŸ release-v2๏ผˆ2B/9B ใƒขใƒ‡ใƒซใฎๅญฆ็ฟ’ใซไฝฟ็”จ๏ผ‰ใฏ 80,816 ไปถใฎๅญฆ็ฟ’่กŒ ใจใ€ๅ…จๅˆ†ๅ‰ฒใง 115,821 ่กŒ ใ‚’ๆŒใคใ€‚ไธŠ่จ˜ใฎๅ…ฌ้–‹ๆŠ•ๅฝฑใฏใ€ใใฎๆญฃ็ขบใชๅญฆ็ฟ’ใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใงใฏใชใ„ใ€‚2 ใคใฎ่ค‡ๅˆ config ใฏใใ‚Œใžใ‚Œใ€ใกใ‚‡ใ†ใฉ 2,253 ไปถใฎ Wikispeedia ่กŒ ใ‚’้™คๅค–ใ—ใฆใ„ใ‚‹ใ€‚ๅ†…่จณใฏใ€train 1,700ใ€calibration 89ใ€validation 69ใ€test 176ใ€OOD 219ใ€‚ๅ…ƒใฎ expansion ใฎๆททๅˆใฏ 163,050 ่กŒใงใ€ใใฎใ†ใก 110,324 ่กŒใŒ train ใงใ‚ใ‚‹ใ€‚ๅ…ƒใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใจใƒใƒƒใ‚ทใƒฅใฏๆ”นๅค‰ใ›ใšไฟๅญ˜ใ•ใ‚Œใฆใ„ใ‚‹ใ€‚REPRODUCTION.md ใซใฏใ€ๅˆฅ้€”ๅ…ฅๆ‰‹ใ—ใŸใ‚ฝใƒผใ‚นใƒ‡ใƒผใ‚ฟใงไธกๆ–นใฎๅ…ƒใฎๆททๅˆใ‚’ๅพฉๅ…ƒใ™ใ‚‹ๆ–นๆณ•ใŒๆ›ธใ‹ใ‚Œใฆใ„ใ‚‹ใ€‚

citation/entity/amount/email/phone ใฎ 5 ใคใฎใ‚ณใƒผใƒ‘ใ‚นใฏใ€2B/9B ใฎๅฎŸ่กŒใฎๅพŒใซๆบ–ๅ‚™ใ•ใ‚Œใ€็›ฃๆŸปใ•ใ‚ŒใŸใ€‚ๆœฌใƒชใƒชใƒผใ‚นๆ™‚็‚นใงใฏใ€ๅญฆ็ฟ’ใซใ‚‚ๅฎŸ้š›ใฎใƒขใƒ‡ใƒซๆŽจ่ซ–ใซใ‚‚ไฝฟใ‚ใ‚Œใฆใ„ใชใ„ใ€‚ expansion ใฎๆททๅˆใฏๅˆฅใฎ 27B ใฎๅฎŸ้จ“ใซๅฑžใ™ใ‚‹ใ€‚ใ“ใฎใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใฎๅ…ฌ้–‹ใฏใ€ใใฎๅฎŸ้จ“ใซใคใ„ใฆๅญฆ็ฟ’ใฎๅฎŒไบ†ใ‚„ๆ€ง่ƒฝใฎไธปๅผตใ‚’ใ—ใชใ„ใ€‚

่ชญใฟ่พผใฟใจๅพฉๅท

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"])

ๅ†็พๆ€งใฎใŸใ‚ใ€revision="<dataset commit SHA>" ใ‚’ๆธกใ™ใ€‚config ใฏๆ˜Ž็คบ็š„ใซ้ธใถใ“ใจใ€‚ๆ—ขๅฎšใ‚’่ชญใฟ่พผใ‚“ใงใ‚‚ใ€ๅˆฅใฎๅˆถๅพกใ‚ณใƒผใƒ‘ใ‚นใฏๅซใพใ‚Œใชใ„ใ€‚

Column ๆ„ๅ‘ณ
id, group_id, split, source ๅ…ƒใฎๅŒไธ€ๆ€งใ€ใ‚ฐใƒซใƒผใƒ—ๅŒ–ใ€ๅˆ†ๅ‰ฒใ€็”Ÿๆˆๅ…ƒใƒปใ‚ฝใƒผใ‚นใฎใƒใƒผใ‚ธใƒงใƒณใ€‚
kind ๅ…ƒใฎๅˆคๆ–ญใฎๅž‹ใ€‚ใ‚ฝใƒผใ‚นใฎใ‚ฟใ‚นใ‚ฏๅฎš็พฉใซ็…งใ‚‰ใ—ใฆ่งฃ้‡ˆใ™ใ‚‹ใ“ใจใ€‚
question, options ใƒขใƒ‡ใƒซใซ่ฆ‹ใˆใ‚‹่ณชๅ•ใจใ€้ †ๅบไป˜ใใฎ่งฃ็ญ”็ฉบ้–“ใ€‚
target ๅ…ƒใฎๆ•ฐๅ€คใฎๅ‚็…งใ‚ฟใƒผใ‚ฒใƒƒใƒˆใ€‚float64 ใฎใƒชใ‚นใƒˆใจใ—ใฆ่กจใ™ใ€‚ใ“ใ‚Œใ‚‰ใฏใƒฉใƒ™ใƒซใงใ‚ใ‚Šใ€ๆธฌๅฎšใ•ใ‚ŒใŸใƒขใƒ‡ใƒซใฎ็ขบไฟกๅบฆใงใฏใชใ„ใ€‚
state_json ๅ…ƒใฎ็Šถๆ…‹ใ‚’ JSON ใง็ฌฆๅทๅŒ–ใ—ใŸใ‚‚ใฎใ€‚ๅพฉๅทใ™ใ‚‹ใจใ€ใ‚ฝใƒผใ‚นใซใ‚ˆใฃใฆๆ–‡ๅญ—ๅˆ—ใพใŸใฏๆง‹้€ ๅŒ–ใ‚ชใƒ–ใ‚ธใ‚งใ‚ฏใƒˆใŒ่ฟ”ใ‚‹ใ€‚
metadata_json ๅ…ƒใฎ็”ฑๆฅใจ็›ฃๆŸปใฎใƒกใ‚ฟใƒ‡ใƒผใ‚ฟใ€‚็‰นๆจฉ็š„ใช teacher/control ใƒฉใƒ™ใƒซใ‚’ๅซใ‚€ใ“ใจใŒใ‚ใ‚Šใ€ใƒขใƒ‡ใƒซใฎๅ…ฅๅŠ›ใซไฝฟใฃใฆใฏใชใ‚‰ใชใ„ใ€‚
record_json ๅ…ƒใฎ JSON ใƒฌใ‚ณใƒผใƒ‰ใ‚’ๅฎŒๅ…จใซไฟๆŒใ—ใŸใ‚‚ใฎใ€‚ใ‚ชใƒ–ใ‚ธใ‚งใ‚ฏใƒˆใฎใ‚ญใƒผใฎ้ †ๅบใจๆ•ฐๅ€คใฎ่กจ็พใ‚’ๅ…ƒใฎใพใพๆฎ‹ใ™ใ€‚
original_line_number ๅ…ƒใฎๅ‡็ตใ•ใ‚ŒใŸๅˆ†ๅ‰ฒใซใŠใ‘ใ‚‹ 1 ๅง‹ใพใ‚Šใฎ่กŒไฝ็ฝฎใ€‚้™คๅค–ใ•ใ‚ŒใŸ่กŒใฎไฝ็ฝฎใ‚‚ๅซใ‚€ใ€‚

Parquet ใฎ่กจ็พใฏใ€็•ฐใชใ‚‹ใ‚ฟใ‚นใ‚ฏใฎ็Šถๆ…‹ใซ 1 ใคใฎๅ…ฅใ‚Œๅญใฎใ‚นใ‚ญใƒผใƒžใ‚’ๆŠผใ—ไป˜ใ‘ใชใ„ใ‚ˆใ†ใซใ—ใฆใ„ใ‚‹ใ€‚raw/<config>/<split>.jsonl.gz ใฏใ€ๅฑ•้–‹ๅพŒใซใ‚ฝใƒผใ‚นใฎ JSONL ใฎใƒใ‚คใƒˆๅˆ—ใ‚’ไฟๆŒใ™ใ‚‹ใ€‚ใƒ•ใ‚ฃใƒซใ‚ฟๆธˆใฟใฎ่ค‡ๅˆ config ใงใฏใ€ๆฎ‹ใ•ใ‚ŒใŸ่กŒใฏใƒใ‚คใƒˆๅˆ—ใจ้ †ๅบใ‚’ๆญฃ็ขบใซไฟใคใ€‚ๅ˜็‹ฌใฎๅˆถๅพก config 10 ๅ€‹ใซใคใ„ใฆใฏใ€ๅฑ•้–‹ใ—ใŸใƒ•ใ‚กใ‚คใƒซใŒๅ…ƒใฎๅ‡็ตใ•ใ‚ŒใŸๅˆ†ๅ‰ฒใฎใƒใƒƒใ‚ทใƒฅใจๆญฃ็ขบใซไธ€่‡ดใ™ใ‚‹ใ€‚

ใƒขใƒ‡ใƒซใฎๅ…ฅๅŠ›ใจใ—ใฆไฝฟใ†ใฎใฏ stateใ€questionใ€kindใ€options ใ ใ‘ใซใ™ใ‚‹ใ“ใจใ€‚targetใ€metadataใ€ๅŒไธ€ๆ€งใ€ๅˆ†ๅ‰ฒใฎๅ‰ฒใ‚Šๅฝ“ใฆใ€็”ฑๆฅใฎใƒ•ใ‚ฃใƒผใƒซใƒ‰ใ‚’ใƒขใƒ‡ใƒซใซ่ฆ‹ใ›ใฆใฏใชใ‚‰ใชใ„ใ€‚ๅˆ†ๅธƒใƒปไบŒๅ€คใƒปๅคšใƒฉใƒ™ใƒซใƒป้ †ๅบใฎใ‚ฟใƒผใ‚ฒใƒƒใƒˆใฏๆ„ๅ‘ณใŒ็•ฐใชใ‚‹ใ€‚ใ™ในใฆใฎ่กŒใ‚’ๅ˜ไธ€ใ‚ฏใƒฉใ‚นใฎๆญฃ่งฃ็އใฎ่จˆ็ฎ—ใซ้‚„ๅ…ƒใ—ใฆใฏใชใ‚‰ใชใ„ใ€‚

้ ˜ๅŸŸใจๆง‹็ฏ‰

  • ๅŸบๆœฌใฎใƒชใƒชใƒผใ‚นใฏใ€็ตฑๅˆถใ•ใ‚ŒใŸ้กงๅฎขใ‚ตใƒใƒผใƒˆใฎใƒซใƒผใƒ†ใ‚ฃใƒณใ‚ฐใจใƒˆใƒชใ‚ขใƒผใ‚ธใ€ใƒญใƒผใ‚ซใƒซใชใƒฏใƒผใ‚ฏใƒ•ใƒญใƒผใฎๅˆคๆ–ญใ€ๅนพไฝ•ๅญฆ็š„ใช็ตต็”ปใฎ็ขบ็އใฎ่ฆๆฑ‚ใ€Snake ใจไธ‰็›ฎไธฆในใ€็ฐก็•ฅๅŒ–ใ•ใ‚ŒใŸ T-Rex/runner ใจใƒ—ใƒฉใƒƒใƒˆใƒ•ใ‚ฉใƒผใƒžใƒผใฎๆ“ไฝœใ€ๆ•ฐๅ€คใฎ ViZDoom Basic ใฎ่ปŒ่ทกใ€็ตฑๅˆถใ•ใ‚ŒใŸๆŽจ่ซ–ใฎๅˆคๆ–ญใ‚’ๆ‰ฑใ†ใ€‚
  • expansion ใซใฏใ€็ตฑๅˆถใ•ใ‚ŒใŸใƒ–ใƒฉใ‚ฆใ‚ถใฎ็Šถๆ…‹ใƒปๆ“ไฝœใจใ€ใƒ‰ใƒญใƒผใƒณใฎ็Šถๆ…‹ใƒปๅˆถๅพกใฎไพ‹ใŒใ•ใ‚‰ใซๅซใพใ‚Œใ‚‹ใ€‚ใ“ใ‚Œใ‚‰ใฏๅฎฃ่จ€ใ•ใ‚ŒใŸใ‚ทใƒŸใƒฅใƒฌใƒผใ‚ทใƒงใƒณใฎใ‚ฟใ‚นใ‚ฏๅฝขๅผใ‚’่กจใ™ใ‚‚ใฎใงใ‚ใ‚Šใ€ๅˆถ้™ใฎใชใ„ใƒ–ใƒฉใ‚ฆใ‚ถใฎๅˆฉ็”จใ‚„ๅฎŸๆฉŸใฎ่ˆช็ฉบๆฉŸใฎๆ“็ธฆใงใฏใชใ„ใ€‚
  • citation ใฎใƒ‡ใƒผใ‚ฟใฏใ€ๅ…ƒใฎๆ–น้‡ๆ–‡ๆ›ธใ€ๅผ•็”จใ€่ฆ‹ใˆใ‚‹ไบ‹ๅฎŸใจไธปๅผตใ‚’ไฝฟใ„ใ€supported/contradicted/insufficient ใฎๅˆคๆ–ญใ‚’ไป˜ใ‘ใ‚‹ใ€‚่ฉฆใ•ใ‚Œใ‚‹ใฎใฏ็ตฑๅˆถใ•ใ‚ŒใŸ้–ขไฟ‚ใงใ‚ใ‚Šใ€ไปปๆ„ใฎไบ‹ๅฎŸ็ขบ่ชใงใฏใชใ„ใ€‚
  • entity alignment ใฏใ€ๅ…ƒใฎใ‚ซใ‚ฟใƒญใ‚ฐใฎใƒ•ใ‚กใƒŸใƒชใƒผใ€ใƒฌใ‚ณใƒผใƒ‰ใ€ๅˆฅๅใ€่ฆ‹ใˆใ‚‹็…งๅˆๆ–น้‡ใ‚’ใ€่ค‡ๆ•ฐใฎๅˆคๆ–ญใƒ˜ใƒƒใƒ‰ใจใจใ‚‚ใซไฝฟใ†ใ€‚
  • amountใƒปemailใƒปphone ใฎๆŠฝๅ‡บใฏใ€ๆฑบๅฎš็š„ใชๅ€™่ฃœ็”Ÿๆˆใ‚’ๅž‹ไป˜ใใฎ้ธๆŠžใƒปๅฑžๆ€งใฎๅˆคๆ–ญใ‹ใ‚‰ๅˆ†ใ‘ใฆใ„ใ‚‹ใ€‚ๆ—ข็Ÿฅใฎๅ€™่ฃœใฎๅ–ใ‚Š้€ƒใŒใ—ใจ้ƒจๅˆ†ไธ€่‡ดใฏใ€ๆญฃ่งฃ๏ผˆgold answer๏ผ‰ใ‚’ไฝฟใฃใฆ็ฝฎใๆ›ใˆใšไฟๆŒใ•ใ‚Œใ‚‹ใ€‚ๆกไปถไป˜ใใฎๅฑžๆ€งใƒ˜ใƒƒใƒ‰ใจใ€็œใ‹ใ‚ŒใŸๆ•™ๅธซใฎไปถๆ•ฐใฏๅ…ƒใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใซ่จ˜้Œฒใ•ใ‚Œใฆใ„ใ‚‹ใ€‚

ๆ–ฐใ—ใ„ใ‚ณใƒผใƒ‘ใ‚นใฏใ€artifacts/ ใซๅœง็ธฎใ•ใ‚ŒใŸๆ–‡ๆ›ธใƒปใƒ•ใ‚กใƒŸใƒชใƒผใƒปใ‚ฑใƒผใ‚นใ‚’ๅซใ‚€ใ€‚ใ“ใ‚Œใ‚‰ใฏๅ†็พใจ็›ฃๆŸปใฎใŸใ‚ใฎๆˆๆžœ็‰ฉใงใ‚ใ‚Šใ€ๅˆ่จˆใซๅŠ ใˆใ‚‹ๅž‹ไป˜ใใฎ่กŒใงใฏใชใ„ใ€‚citation ใฏ 200 ๆ–‡ๆ›ธใจ 4,400 ใ‚ฑใƒผใ‚นใ‚’ๆŒใคใ€‚ๅ†…่จณใฏใ€4,000 ใฎๅž‹ไป˜ใใฎๆ„ๅ‘ณใ‚ฑใƒผใ‚นใจใ€400 ใฎใ€Œๅผ•็”จใŒ่ฆ‹ใคใ‹ใ‚‰ใชใ„ใ€็ตฑๅˆถใ‚ฑใƒผใ‚นใ€‚entity alignment ใฏ 200 ใƒ•ใ‚กใƒŸใƒชใƒผใจ 2,800 ใ‚ฑใƒผใ‚นใ€amount ใฏ 200 ใƒ•ใ‚กใƒŸใƒชใƒผใจ 3,200 ๆ–‡ๆ›ธใ€email ใฏ 200 ใƒ•ใ‚กใƒŸใƒชใƒผใจ 2,800 ๆ–‡ๆ›ธใ€phone ใฏ 200 ใƒ•ใ‚กใƒŸใƒชใƒผใจ 4,000 ๆ–‡ๆ›ธใ‚’ๆŒใคใ€‚

ๅ…ƒใฎใƒ‡ใƒผใ‚ฟใจๅˆ†ๅ‰ฒใฎๆ–น้‡ใฏใ€ใ‚ณใƒผใƒ‘ใ‚นใ”ใจใซ provenance/original-manifests/ ใซ่จ˜้Œฒใ•ใ‚Œใฆใ„ใ‚‹ใ€‚้–ข้€ฃใ™ใ‚‹ๆ–‡ๆ›ธใƒปใ‚จใƒณใƒ†ใ‚ฃใƒ†ใ‚ฃใƒป่ปŒ่ทกใฏใ€ๅˆ†ๅ‰ฒใฎไธญใงใ‚ฐใƒซใƒผใƒ—ๅŒ–ใ•ใ‚ŒใŸใพใพๆฎ‹ใ‚‹ใ€‚OOD ใฏใ‚ฝใƒผใ‚นใ”ใจใฎใ‚‚ใฎใงใ€ใ‚ˆใไบˆ็ด„ใ•ใ‚ŒใŸ่จ€ใ„ๅ›žใ—ใ€ใƒฌใ‚คใ‚ขใ‚ฆใƒˆใ€ๅˆถๅพกใฎใƒ•ใ‚กใƒŸใƒชใƒผใ‚„็›ฎๆจ™ใงใ‚ใ‚Šใ€ๆ™ฎ้็š„ใชๆœช็Ÿฅ้ ˜ๅŸŸใฎใƒ™ใƒณใƒใƒžใƒผใ‚ฏใงใฏใชใ„ใ€‚ใƒญใƒผใ‚ซใƒซใฎใ‚จใ‚ฏใ‚นใƒใƒผใƒˆๆคœ่จผใฏใ€config ใ”ใจใซ ID ใฎไธ€ๆ„ๆ€งใจใ€ๅˆ†ๅ‰ฒใ‚’ใพใŸใใ‚ฐใƒซใƒผใƒ—ใฎๅˆ†้›ขใ‚’็ขบใ‹ใ‚ใ‚‹ใ€‚

่ฉ•ไพกใฎๅขƒ็•Œ

trainใƒปcalibrationใƒปvalidationใƒปtestใƒปOOD ใฏๅˆฅใ€…ใซๅ…ฌ้–‹ใ•ใ‚Œใ‚‹ใ€‚train ๅˆ†ๅ‰ฒใงๅญฆ็ฟ’ใ™ใ‚‹ใ“ใจใ€‚calibration ใฏๅฎฃ่จ€ใ•ใ‚ŒใŸ calibration ใฎๆ‰‹้ †ใซใฎใฟไฝฟใ„ใ€validation ใฏใƒขใƒ‡ใƒซใฎ้ธๆŠžใซไฝฟใ†ใ€‚test ใจ OOD ใฎใƒฉใƒ™ใƒซใฏๅ…ฌ้–‹ใ•ใ‚Œใฆใ„ใ‚‹ใŸใ‚ใ€ไปŠๅพŒใฎ็ ”็ฉถใฏ้–‹็™บใซใใ‚Œใ‚‰ใ‚’ไฝฟใฃใŸๅ ดๅˆใซใใฎๆ—จใ‚’ๆ˜Ž่จ˜ใ—ใชใ‘ใ‚Œใฐใชใ‚‰ใชใ„ใ€‚ๅ…ƒใฎๅ‡็ตใ•ใ‚ŒใŸๆททๅˆๅ…จไฝ“ใงๆธฌใฃใŸใ‚นใ‚ณใ‚ขใฏใ€ๅ†่จˆ็ฎ—ใชใ—ใซใ€ใ“ใฎๅฐใ•ใชๅ…ฌ้–‹ๆŠ•ๅฝฑใฎใ‚นใ‚ณใ‚ขใจใ—ใฆ่จ˜่ฟฐใ—ใฆใฏใชใ‚‰ใชใ„ใ€‚

Jev Frontier 100 ใฎ่ณชๅ•ใƒปๅ›ž็ญ”ใฎใƒšใ‚คใƒญใƒผใƒ‰ใฏๅซใพใ‚Œใฆใ„ใชใ„ใ€‚ๅค–้ƒจใฎ jev-frontier-100 ใƒ™ใƒณใƒใƒžใƒผใ‚ฏ ใฏใ€ๅญฆ็ฟ’ใจ็”Ÿๆˆใ‹ใ‚‰ใฏๅˆ‡ใ‚Š้›ขใ•ใ‚ŒใŸใพใพใงใ‚ใ‚‹ใ€‚ๅ…ฌๅผใฎ้žๅ…ฌ้–‹ใฎไพ‹ใ€ใ‚ฒใƒผใƒ ใฎ ROMใ€ใ‚ฒใƒผใƒ ใฎใ‚ขใ‚ปใƒƒใƒˆใ€ใƒขใƒ‡ใƒซใฎ้‡ใฟใ€่ช่จผๆƒ…ๅ ฑใฏๅซใพใ‚Œใฆใ„ใชใ„ใ€‚

ใƒฉใ‚คใ‚ปใƒณใ‚นใจ็”ฑๆฅ

ๅ…ƒใฎ็”Ÿๆˆใƒฌใ‚ณใƒผใƒ‰ใฏใ€ๆ—ขๅญ˜ใฎ็”ฑๆฅๆƒ…ๅ ฑใง CC0-1.0 ใจๆ˜Ž่จ˜ใ•ใ‚Œใฆใ„ใ‚‹ใ€‚CC0 ใซใ‚ˆใ‚‹ๅ…ฌๆœ‰ๅŒ–ใฎๅฎฃ่จ€ใŒๅŠใถใฎใฏใ€็งใŸใกใŒ็”Ÿๆˆใ—ใŸๅ†…ๅฎนใงใ‚ใ‚Šใ€ไธŠๆตใฎๆ–‡่จ€ใ€ๅค–้ƒจใฎใ‚ขใ‚ปใƒƒใƒˆใ€ใ‚ฝใƒผใ‚นใƒ‡ใƒผใ‚ฟใ€ใƒขใƒ‡ใƒซใฎ้‡ใฟใซใฏๅŠใฐใชใ„ใ€‚ๅ…ƒใฎใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฏ MIT ใงใ‚ใ‚‹ใ€‚customer-control ใฎ็”ฑๆฅใซใฏใ€ไธŠๆตใฎ็Ÿญใ„่ณชๅ•่ชฌๆ˜ŽใŒใ€ๆคœ่จผๆธˆใฟใฎใ‚ฝใƒผใ‚นใƒฉใ‚คใ‚ปใƒณใ‚นใฎใชใ„ TypeSafe ใฎใƒ‰ใ‚ญใƒฅใƒกใƒณใƒˆ็”ฑๆฅใงใ‚ใ‚‹ใจใ„ใ†ๅ…ƒใฎๆณจ่จ˜ใŒๆฎ‹ใ•ใ‚Œใฆใ„ใ‚‹ใ€‚ๆœฌใƒชใƒชใƒผใ‚นใฏใใ‚Œใ‚‰ใฎ่ชฌๆ˜Žใฎใƒฉใ‚คใ‚ปใƒณใ‚นใ‚’ๆ”นใ‚ใฆไป˜ไธŽใ—ใชใ„ใ€‚่ฉณใ—ใใฏ THIRD_PARTY_NOTICES.md ใ‚’ๅ‚็…งใ€‚

Wikispeedia ใ‚ขใƒผใ‚ซใ‚คใƒ– ใฏใ€ๆคœ่จผๆธˆใฟใฎใ€ใ‚ฐใƒฉใƒ•ใƒปใƒ‘ใ‚นใฎๅ†้…ๅธƒใซ้–ขใ™ใ‚‹ๅˆฅใฎใƒฉใ‚คใ‚ปใƒณใ‚นใ‚’ๅฎฃ่จ€ใ—ใฆใ„ใชใ„ใ€‚ใ—ใŸใŒใฃใฆใ€ใใฎใ‚ฟใ‚นใ‚ฏใฎ่กŒใฏ 2 ใคใฎๅ…ฌ้–‹ๆททๅˆใฎๆŠ•ๅฝฑใ‹ใ‚‰้™คๅค–ใ—ใฆใ„ใ‚‹ใ€‚็พๅœจใฎ Wikipedia ใฎใƒฉใ‚คใ‚ปใƒณใ‚นใŒใ€ใ‚ขใƒผใ‚ซใ‚คใƒ–ใ•ใ‚ŒใŸใ‚ฐใƒฉใƒ•ใƒปใƒ‘ใ‚นใฎใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใ‚’่ฆ†ใ†ใจใฏๆŽจๅฎšใ—ใชใ„ใ€‚ๅ…ƒใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใ€ใ‚ฝใƒผใ‚น URLใ€ใ‚ขใƒผใ‚ซใ‚คใƒ–ใฎ SHA-256ใ€ๆญฃ็ขบใช้™คๅค–ไฝ็ฝฎใ€ใƒญใƒผใ‚ซใƒซใฎๅ†ๆง‹ๆˆใƒฆใƒผใƒ†ใ‚ฃใƒชใƒ†ใ‚ฃใฏๅ…ฌ้–‹ใ™ใ‚‹ใŒใ€ใ‚ฐใƒฉใƒ•ใ€ใƒ‘ใ‚นใ€ใ‚ฟใ‚นใ‚ฏใฎใƒšใ‚คใƒญใƒผใƒ‰ใฏๅ…ฌ้–‹ใ—ใชใ„ใ€‚

Wikispeedia ใฎๅ‚่€ƒๆ–‡็Œฎ:

  • 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 ใซใฏใ€ๅ…ƒใฎๅˆ†ๅ‰ฒใจๅ…ฌ้–‹ใฎๅˆ†ๅ‰ฒใฎไปถๆ•ฐใจใƒใƒƒใ‚ทใƒฅใ€ใ‚ฝใƒผใ‚นใฎไปถๆ•ฐใ€้™คๅค–ไฝ็ฝฎใ€ใ‚ฝใƒผใ‚นใ‚ณใƒผใƒ‰ใฎใƒ•ใ‚ฃใƒณใ‚ฌใƒผใƒ—ใƒชใƒณใƒˆใ€ๅ…ฌ้–‹ใ•ใ‚ŒใŸใƒ•ใ‚กใ‚คใƒซใฎใƒใƒƒใ‚ทใƒฅใŒ่จ˜้Œฒใ•ใ‚Œใฆใ„ใ‚‹ใ€‚REPRODUCTION.md ใซใฏใ€ๆญฃ็ขบใชๅพฉๅ…ƒใจ็”Ÿๆˆใฎใ‚ณใƒžใƒณใƒ‰ใŒๆ›ธใ‹ใ‚Œใฆใ„ใ‚‹ใ€‚ใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใƒชใƒใ‚ธใƒˆใƒชใฎ Git ใ‚ณใƒŸใƒƒใƒˆใŒใ€ใ“ใฎๅฎŒๅ…จใชใƒชใƒชใƒผใ‚นใ‚’ๅ›บๅฎšใ—ใฆใ„ใ‚‹ใ€‚

ใ‚ณใƒŸใƒฅใƒ‹ใƒ†ใ‚ฃใฎใ‚ฟใ‚นใ‚ฏ่ฟฝๅŠ  โ€” 2026-09-20

CC0 ใฎๅ…ƒใฎๅˆถๅพก config ใ‚’ 3 ใค่ฟฝๅŠ ใ—ใ€15 ใฎๆ–ฐใ—ใ„ๅˆ†ๅ‰ฒใซใพใŸใŒใ‚‹ 30,234 ใฎๅž‹ไป˜ใใฎ่กŒ ใ‚’ๅŠ ใˆใŸใ€‚ใ“ใฎ่ฟฝๅŠ ใซใ‚ˆใ‚Šใ€ใƒชใƒใ‚ธใƒˆใƒชใฏ 10 configใƒป50 ๅˆ†ๅ‰ฒ ใซใชใฃใŸใ€‚ๆ—ขๅญ˜ใฎ configใ€ใƒšใ‚คใƒญใƒผใƒ‰ใ€ใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใ€ๆ—ขๅฎšใฎ config ใฏๅค‰ใ‚ใ‚‰ใชใ„ใ€‚

ใ“ใ‚Œใ‚‰ 3 ใคใฎ่ฟฝๅŠ ใฏใ€ๅญฆ็ฟ’ใซใ‚‚ใƒขใƒ‡ใƒซใฎ่ฉ•ไพกใซใ‚‚ไฝฟใ‚ใ‚Œใฆใ„ใชใ„ใ€‚ ็‹ฌ็ซ‹ใ—ใŸใƒ‡ใƒผใ‚ฟ็›ฃๆŸปใŒใ€ๅ‚็…งใƒฉใƒ™ใƒซใจๅˆ†ๅ‰ฒใฎๆ•ดๅˆๆ€งใ‚’ๆคœ่จผใ—ใฆใ„ใ‚‹ใ€‚ใŸใ ใ—ใƒขใƒ‡ใƒซใฎใƒ™ใƒณใƒใƒžใƒผใ‚ฏใงใฏใชใ„ใ€‚ๅ…ฌ้–‹ใ•ใ‚ŒใŸ 2B/9B ใฎๅญฆ็ฟ’ๆททๅˆใฏๅค‰ใ‚ใ‚‰ใชใ„ใ€‚

  • context-retention-control-v1: ๅฏพ่ฑกใจใชใ‚‹ๅฎŒไบ†ๆธˆใฟใฎใƒ„ใƒผใƒซๅ‘ผใณๅ‡บใ—ใฎ่จ˜้Œฒใจๅ…จๅ‡บๅŠ›ใ‚’ใ€ๆ˜Ž็คบ็š„ใงๅ›บๅฎšใ•ใ‚ŒใŸไฟๆŒๆ–น้‡ใฎใ‚‚ใจใงๆฎ‹ใ™ใ‹ๆจใฆใ‚‹ใ‹ใ‚’ๅˆคๆ–ญใ™ใ‚‹ใ€‚ๅ…ฑๆœ‰ใ•ใ‚Œใ‚‹็Šถๆ…‹ใฏๆ–‡่„ˆใƒป็›ฎๆจ™ใƒปๅฑฅๆญดใ‚’ๅซใฟใ€ใƒ„ใƒผใƒซใฎๅ…จๅ‡บๅŠ›ใฏ็œใ‹ใ‚Œใ‚‹ใ€‚ๅฏพ่ฑกใฎๅ‘ผใณๅ‡บใ— 1 ไปถใ”ใจใซ 2 ใคใฎ Noul ใฎ่ณชๅ•ใ‚’ไฝœใ‚‹ใ€‚ใƒฉใƒ™ใƒซใฏใ€็›ฎใซ่ฆ‹ใˆใ‚‹็›ฎๆจ™ใฎไพๅญ˜ใฎ้–‰ๅŒ…ใ€ๆญฃ็ขบใช่จผๆ‹ ใฎๅฟ…่ฆๆ€งใ€ๅ‡บๅŠ›ใฎๅ›žๅพฉๅฏ่ƒฝๆ€งใซๅพ“ใ†ใ€‚ๅ›บๅฎšใ•ใ‚ŒใŸ๏ผˆpinned๏ผ‰ๅ‘ผใณๅ‡บใ—ใจไฟ็•™ไธญ๏ผˆpending๏ผ‰ใฎๅ‘ผใณๅ‡บใ—ใฏใ‚ฝใƒ•ใƒˆใ‚ฆใ‚งใ‚ขใฎใ‚ฒใƒผใƒˆใงใ‚ใ‚Šใ€ใƒขใƒ‡ใƒซใฎใƒฉใƒ™ใƒซใฏใชใ„ใ€‚ใ‚ฟใ‚นใ‚ฏใ‚ฐใƒฉใƒ•ๅ…จไฝ“ใจใ€ใใฎ็›ฎๆจ™ใƒปๅ›žๅพฉๅฏ่ƒฝๆ€งใฎๅๅฎŸไปฎๆƒณใฏๅŒใ˜ๅˆ†ๅ‰ฒใ‚’ๅ…ฑๆœ‰ใ™ใ‚‹ใ€‚OOD ใฏใ€ใƒ€ใ‚คใƒคใƒขใƒณใƒ‰ๅž‹ใฎไพๅญ˜ใจ่จ€ใ„ๅ›žใ—ใ‚’ไบˆ็ด„ใ™ใ‚‹ใ€‚ใ“ใฎๆœ‰้™ใฎๅˆๆˆใ‚ฟใ‚นใ‚ฏใฏใ€ๆœ‰็”จใชไปปๆ„ใฎใ‚ปใƒƒใ‚ทใƒงใƒณใฎๅœง็ธฎใฎ่จผๆ‹ ใงใฏใชใ„ใ€‚
  • sponsor-segment-control-v1: ๅ…ƒใฎใ‚ฟใ‚คใƒ ใ‚นใ‚ฟใƒณใƒ—ไป˜ใใฎๆ›ธใ่ตทใ“ใ—ใฎๅŒบ้–“ใ‚’ใ€ๅŒบ้–“ใ”ใจใซ 1 ใคใฎ Choice ใงๅˆ†้กžใ™ใ‚‹ใ€‚ๅˆ†้กžใฏ sponsorใ€self_promoใ€introใ€outroใ€recapใ€contentใ€otherใ€‚ๆœ‰ๅ„Ÿใฎ็ฌฌไธ‰่€…ใซใ‚ˆใ‚‹ๅฎฃไผใซใฏใ€่ณ‡้‡‘ๆไพ›ใŒใ‚ใฃใŸใจใ„ใ†ๆ˜Ž็ขบใช่จผๆ‹ ใŒๅฟ…่ฆใงใ‚ใ‚‹ใ€‚ใ‚ฏใƒชใ‚จใ‚คใ‚ฟใƒผ่‡ช่บซใฎๅฎฃไผใฏๅˆฅๆ‰ฑใ„ใ€‚ใƒ–ใƒฉใƒณใƒ‰ๅใ€ๅ‰ฒๅผ•ใ‚ณใƒผใƒ‰ใ€ใƒ—ใƒญใƒขใฎใƒžใƒผใ‚ซใƒผใ ใ‘ใงใฏใ€ใ‚นใƒใƒณใ‚ตใƒผใงใ‚ใ‚‹ใจใฏ็ขบๅฎšใ—ใชใ„ใ€‚ๅ‹•็”ปใฎใƒ•ใ‚กใƒŸใƒชใƒผๅ…จไฝ“ใจๆ”ฏๆ‰•ใ„ใฎ่จผๆ‹ ใฎๅๅฎŸไปฎๆƒณใฏใ€ๅŒใ˜ๅˆ†ๅ‰ฒใ‚’ๅ…ฑๆœ‰ใ™ใ‚‹ใ€‚OOD ใฏๆ–‡ๅ…จไฝ“ใฎ่จ€ใ„ๅ›žใ—ใ‚’ไบˆ็ด„ใ™ใ‚‹ใ€‚ใƒ‡ใƒผใ‚ฟใฏๆœ‰้™ใฎๅˆๆˆใฎๆ›ธใ่ตทใ“ใ—ใงใ‚ใ‚Šใ€ใ‚นใ‚ฏใƒฌใ‚คใƒ”ใƒณใ‚ฐใ—ใŸๅ‹•็”ปใ‚„ใ€้Ÿณๅฃฐใƒปๆ˜ ๅƒใฎใƒ™ใƒณใƒใƒžใƒผใ‚ฏใงใฏใชใ„ใ€‚
  • silent-failure-control-v1: ๆญฃ็ขบใชใƒฌใ‚นใƒใƒณใ‚นๆœฌๆ–‡ใฎๆ–‡ๅญ—ๅˆ—ใฎใฟใ‚’ไฝฟใฃใฆใ€is_silent_failure ใฎ Noul ใฎ่ณชๅ•ใ‚’ 1 ใคๅฐ‹ใญใ‚‹ใ€‚ใƒˆใƒฉใƒณใ‚นใƒใƒผใƒˆใฎใ‚นใƒ†ใƒผใ‚ฟใ‚นใฏใƒขใƒ‡ใƒซใฎๅ…ฅๅŠ›ใฎๅค–ใซใ‚ใ‚‹ใ€‚็พๅœจใฎใƒกใƒณใƒ†ใƒŠใƒณใ‚นใ€ๆฅญๅ‹™ไธŠใฎๆ‹’ๅฆใ€่ฆๆฑ‚ใ•ใ‚ŒใŸใƒ‡ใƒผใ‚ฟใฎไปฃใ‚ใ‚Šใซใ‚ตใ‚คใƒณใ‚คใƒณใƒšใƒผใ‚ธใŒ่ฟ”ใ‚‹ใ“ใจใ€ๆ˜Ž็คบ็š„ใซๅฟ…่ฆใจใ•ใ‚ŒใŸๅ—้ ˜ๆ›ธใฎๆฌ ่ฝใ€ๆบ€ใŸใ•ใ‚Œใฆใ„ใชใ„้…้€ใฎ่ฆไปถใฏใ€ๆœ‰ๅŠนใช็ฉบใฎ็ตๆžœใ€ๅ›žๅพฉใ•ใ‚ŒใŸๅฑฅๆญดใ€ๅผ•็”จใ•ใ‚ŒใŸใ‚จใƒฉใƒผๆ–‡ใ€ๅ—็†ใ•ใ‚ŒใŸใ‚ญใƒฅใƒผใฎใ‚ธใƒงใƒ–ใ€่จฑๅฏใ•ใ‚ŒใŸ้ƒจๅˆ†็š„ใช็ตๆžœใจๅฏพๆฏ”ใ•ใ‚Œใ‚‹ใ€‚ใƒˆใƒฉใƒณใ‚นใƒใƒผใƒˆใฎๅคฑๆ•—ใฏใ€ๆฑบใ—ใฆๅฆๅฎšใฎๆญฃ่งฃใซใฏใชใ‚‰ใชใ„ใ€‚ใƒ—ใƒญใƒใ‚คใƒ€ใƒปๅฅ‘็ด„ใฎใƒ•ใ‚กใƒŸใƒชใƒผๅ…จไฝ“ใฏใ™ในใฆใฎๅๅฎŸไปฎๆƒณใ‚’ไฟๆŒใ—ใ€OOD ใฏไธญๅ›ฝ่ชžใฎ่จ€ใ„ๅ›žใ—ใจใ€็•ฐใชใ‚‹ JSONใƒปHTMLใƒปใƒ†ใ‚ญใ‚นใƒˆใฎใƒฌใ‚คใ‚ขใ‚ฆใƒˆใ‚’ไบˆ็ด„ใ™ใ‚‹ใ€‚ใ“ใฎ็ตฑๅˆถใ•ใ‚ŒใŸๆ–‡ๆณ•ใฏใ€ไปปๆ„ใฎ API ใฎๆญฃใ—ใ•ใ‚’็คบใ™ใ‚‚ใฎใงใฏใชใ„ใ€‚

ๆ–ฐใ—ใ„ๅ…ƒใฎใ‚ฑใƒผใ‚นใฏใ€ๅˆฅๅ€‹ใฎ็›ฃๆŸปๆˆๆžœ็‰ฉใฎใพใพใงใ‚ใ‚‹ใ€‚Parquet ใฎๅˆ†ๅ‰ฒใซใฏใ€JSONL ใฎๅŽŸๆ–‡ใฎใƒใ‚คใƒˆๅˆ—ใ€ๅ…ƒใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใ€้š”้›ขใ•ใ‚ŒใŸใ‚ฝใƒผใ‚นใฎใ‚นใƒŠใƒƒใƒ—ใ‚ทใƒงใƒƒใƒˆใŒๆทปใˆใ‚‰ใ‚Œใฆใ„ใ‚‹ใ€‚่ฟฝๅŠ ๅˆ†ใฎใ‚จใ‚ฏใ‚นใƒใƒผใƒˆใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆ ใฏใ“ใ‚Œใ‚‰ใฎ่ฟฝๅŠ ใฎใฟใ‚’่จ˜้Œฒใ™ใ‚‹ใ€‚ๅ…ƒใฎ export-manifest.json ใฏใƒใ‚คใƒˆๅ˜ไฝใงไฟๆŒใ•ใ‚Œใฆใ„ใ‚‹ใ€‚

ๅ…ƒใฎ retrieval ๅˆถๅพกใฎ่ฟฝๅŠ  โ€” 2026-09-20

ir-control-v1 ใฏใ€5 ใคใฎๅˆ†ๅ‰ฒใซใพใŸใŒใ‚‹ 11,600 ใฎๅž‹ไป˜ใใฎ่กŒ ใ‚’ๅŠ ใˆใ‚‹ใ€‚ ใ“ใ‚Œใฏ 8,800 ใฎใƒชใ‚ฏใ‚จใ‚นใƒˆใ€400 ใฎใ‚ฏใ‚จใƒชใ€200 ใฎๅฎŒๅ…จใชๆžถ็ฉบใฎใ‚ทใ‚นใƒ†ใƒ ใฎใƒ•ใ‚กใƒŸใƒชใƒผใ‚’่กจใ™ใ€‚ ใ“ใฎ่ฟฝๅŠ ใซใ‚ˆใ‚Šใ€ใƒชใƒใ‚ธใƒˆใƒชใฏ 11 configใƒป55 ๅˆ†ๅ‰ฒ ใซใชใฃใŸใ€‚ ๅ…ƒใฎ 4 ๆฎต้šŽใฎ้–ข้€ฃๆ€งใƒซใƒผใƒ–ใƒชใƒƒใ‚ฏใฎใ‚‚ใจใงใ€pointwise ใฎ Noul/Scoreใ€pairwise/setwise ใฎ Choiceใ€listwise ใฎ Choice/Score ใฎใ‚ฟใ‚นใ‚ฏๅฝขๅผใ‚’ๆ”ฏใˆใ‚‹ใ€‚ Choice ใฎใƒฉใƒ™ใƒซใฏๆœ€่‰ฏใฎใƒ‘ใƒƒใ‚ปใƒผใ‚ธใฎ้ธๆŠžใ‚’ๆ•™ๅธซใ™ใ‚‹ใ‚‚ใฎใงใ‚ใ‚Šใ€้ †ไฝๅ…จไฝ“ใ‚„ไธ็ขบๅฎŸๆ€งใงใฏใชใ„ใ€‚

ใ‚ณใƒผใƒ‘ใ‚นๅ…จไฝ“ใฏใ€ๆœฌๆ–‡ใซ็”ฑๆฅใ™ใ‚‹ใƒฉใƒ™ใƒซใฎ็‹ฌ็ซ‹ใ—ใŸ็›ฃๆŸปใซๅˆๆ ผใ—ใŸใ€‚ใ“ใ‚Œใ‚‰ใฎ IR ใƒฌใ‚ณใƒผใƒ‰ใงๅญฆ็ฟ’ใ—ใŸใจใฏไธปๅผตใ—ใชใ„ใ€‚ๅˆฅ้€”ๅ‡็ตใ•ใ‚ŒใŸ 6 ใ‚ฏใ‚จใƒชใฎ Jev ใƒ‘ใ‚คใƒญใƒƒใƒˆใฏใ€ใ‚ฝใƒผใ‚นใƒ—ใƒญใ‚ธใ‚งใ‚ฏใƒˆใซ่จ˜้Œฒใ•ใ‚Œใฆใ„ใ‚‹ใ€‚ใŸใ ใ—ใ“ใ‚Œใฏใ‚ณใƒผใƒ‘ใ‚นๅ…จไฝ“ใฎ่ฉ•ไพกใงใ‚‚ TREC ใฎ่ฉ•ไพกใงใ‚‚ใชใ„ใ€‚TREC ใฎใƒ‡ใƒผใ‚ฟใ€qrelsใ€ใƒ—ใƒญใƒใ‚คใƒ€ใฎๅฟœ็ญ”ใ€็ฌฌไธ‰่€…ใฎไพ‹ใฏๅซใพใ‚Œใฆใ„ใชใ„ใ€‚ๅ‡็ตใ•ใ‚ŒใŸใƒ‘ใ‚คใƒญใƒƒใƒˆใฎ test/OOD ใฎใƒ•ใ‚กใƒŸใƒชใƒผใฏใ€ๆ‹กๅผตใ•ใ‚ŒใŸใ‚ณใƒผใƒ‘ใ‚นใงใ‚‚ๅ–ใ‚Š็ฝฎใ‹ใ‚ŒใŸใพใพใงใ‚ใ‚‹ใ€‚

ๆ—ขๅญ˜ใฎใƒ‡ใƒผใ‚ฟใ‚ปใƒƒใƒˆใฎใƒšใ‚คใƒญใƒผใƒ‰ใ€ๅ…ƒใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใ€config ใฎๅฎš็พฉใ€ๆ—ขๅฎšใฎ configใ€ๅ‡็ตใ•ใ‚ŒใŸใƒขใƒ‡ใƒซๅญฆ็ฟ’ใฎๆททๅˆใฏใ€ใ™ในใฆๅค‰ใ‚ใ‚‰ใชใ„ใ€‚IR ใฎใ‚จใ‚ฏใ‚นใƒใƒผใƒˆใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆ ใฏใ€ใ“ใฎ่ฟฝๅŠ ใฎใฟใ‚’ๅฏพ่ฑกใจใ™ใ‚‹ใ€‚

ๅ…ƒใฎๅคš่จ€่ชžใฎใƒกใƒผใƒซใƒซใƒผใƒ ่ฟฝๅŠ  โ€” 2026-09-20

mailroom-control-v1 ใฏใ€5 ใคใฎๅˆ†ๅ‰ฒใซใพใŸใŒใ‚‹ 114,800 ใฎๅž‹ไป˜ใใฎ่กŒ ใ‚’ๅŠ ใˆใ‚‹ใ€‚ๅ…ƒใฎใƒกใƒผใƒซ 11,600 ไปถใจใ€่‹ฑ่ชžใƒปไธญๅ›ฝ่ชžใƒปใƒˆใƒซใ‚ณ่ชžใฎๅฎŒๅ…จใชใƒ•ใ‚กใƒŸใƒชใƒผ 400 ใ‹ใ‚‰ไฝœใ‚‰ใ‚Œใ‚‹ใ€‚ใƒชใƒใ‚ธใƒˆใƒชใฏ็พๅœจ 12 configใƒป60 ๅˆ†ๅ‰ฒ ใ‚’ๅฎฃ่จ€ใ—ใฆใ„ใ‚‹ใ€‚ๅ„ใƒชใ‚ฏใ‚จใ‚นใƒˆใฏใ€ใ‚ฝใƒผใ‚นใฎๅฝขใซๅพ“ใฃใŸ 2 ใคใฎ Choice ใจ 9 ใคใฎ Noul ใฎ่ณชๅ•ใ‚’ไฟๆŒใ™ใ‚‹ใ€‚้ž่ซ‹ๆฑ‚ๆ›ธใƒป้ž้ ˜ๅŽๆ›ธใฎใ‚ซใƒ†ใ‚ดใƒชใซใฏๆ•™ๅธซใƒฉใƒ™ใƒซใŒใชใใ€ๅˆ†้กžไฝ“็ณปใฎๅค‰็จฎใ‚’ใพใŸใ„ใงๅค‰ใ‚ใ‚‰ใชใ„ใƒ˜ใƒƒใƒ‰ใฏใ€ๅ…ƒใฎ่กŒใ‚’ๅ…ฑๆœ‰ใ™ใ‚‹ใ€‚้ †ๅบไป˜ใใฎไธ€ๆ„ใชๅ…ฅๅŠ›ใฏ 114,800 ไปถใ€‚ๅ€™่ฃœใฎ้ †ๅบใ‚‚็„ก่ฆ–ใ™ใ‚‹ใจ 114,400 ไปถใซใชใ‚‹ใ€‚

็‹ฌ็ซ‹ใ—ใŸ็›ฃๆŸป่€…ใฏใ€ๆœ€็ต‚็š„ใซ่ฆ‹ใˆใ‚‹ใƒกใƒผใƒซๆœฌๆ–‡ใจๅˆ†้กžไฝ“็ณปใ‹ใ‚‰ใƒฉใƒ™ใƒซใ‚’ๅฐŽใ„ใŸใ€‚ๅ‡็ตใ•ใ‚ŒใŸใƒ—ใƒญใƒผใƒ–ใฎ่กŒใƒปใ‚ฑใƒผใ‚นใฏใ€ใ™ในใฆใƒใ‚คใƒˆๅˆ—ใจๅˆ†ๅ‰ฒใฎๅ‰ฒใ‚Šๅฝ“ใฆใ‚’ไฟใคใ€‚ๅฎŸ้š›ใฎใƒกใƒผใƒซใƒœใƒƒใ‚ฏใ‚นใฎๅ†…ๅฎนใ€้žๅ…ฌ้–‹ใฎใ‚ฝใƒผใ‚นไพ‹ใ€ๆทปไป˜ใƒ•ใ‚กใ‚คใƒซใ€ใƒ—ใƒญใƒใ‚คใƒ€ใฎๅฟœ็ญ”ใฏๅซใพใ‚Œใฆใ„ใชใ„ใ€‚ๅญฆ็ฟ’ใ‚„ใ‚ณใƒผใƒ‘ใ‚นๅ…จไฝ“ใงใฎใƒขใƒ‡ใƒซ่ฉ•ไพกใฏไธปๅผตใ—ใชใ„ใ€‚ๅˆฅ้€”่จ˜้Œฒใ•ใ‚ŒใŸ 87 ใƒชใ‚ฏใ‚จใ‚นใƒˆใฎ Jev ใƒ—ใƒญใƒผใƒ–ใฏใ€ๆœฌ็•ชใฎใƒกใƒผใƒซใฎๆŒฏใ‚Šๅˆ†ใ‘ใฎ็ฒพๅบฆใ‚„ใ€ใƒกใƒผใƒซใƒœใƒƒใ‚ฏใ‚นใฎใ‚จใƒณใƒ‰ใƒ„ใƒผใ‚จใƒณใƒ‰ใฎ่‡ชๅ‹•ๅŒ–ใงใฏใชใ„ใ€‚

ๆ—ขๅญ˜ใฎใƒšใ‚คใƒญใƒผใƒ‰ใ€ใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆใ€config ใฎๅฎš็พฉใ€ๆ—ขๅฎšใฎ configใ€ๅ‡็ตใ•ใ‚ŒใŸๅญฆ็ฟ’ใฎๆททๅˆใฏใ€็›ดๅ‰ใฎ IR ใฎ่ฟฝๅŠ ใ‚’ๅซใ‚ใ€ใ™ในใฆๅค‰ใ‚ใ‚‰ใชใ„ใ€‚mailroom ใฎใ‚จใ‚ฏใ‚นใƒใƒผใƒˆใฎใƒžใƒ‹ใƒ•ใ‚งใ‚นใƒˆ ใฏใ€ใ“ใฎๆ–ฐใ—ใ„ config ใจใใฎ่ฃœๅŠฉ็š„ใช็›ฃๆŸปๆˆๆžœ็‰ฉใฎใฟใ‚’ๅฏพ่ฑกใจใ™ใ‚‹ใ€‚

ๅŽŸๆ–‡๏ผˆ่‹ฑ่ชž๏ผ‰

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
104