set stringclasses 2
values | scenario stringclasses 14
values | condition stringclasses 6
values | setup stringclasses 14
values | you stringclasses 16
values | partner stringlengths 12 246 |
|---|---|---|---|---|---|
main | S1 | cooperative | Two teammates plan a research presentation under time pressure. | YOU: We have one hour. Can we split this so I take the intro and you take the methods? | PARTNER: Yes, that's a good split. I'll add a slide on limitations too --- I think we should be honest about what we don't know. |
main | S1 | neutral | Two teammates plan a research presentation under time pressure. | YOU: We have one hour. Can we split this so I take the intro and you take the methods? | PARTNER: Sure. |
main | S1 | defective | Two teammates plan a research presentation under time pressure. | YOU: We have one hour. Can we split this so I take the intro and you take the methods? | PARTNER: I don't have time. Just do it yourself. |
main | S2 | cooperative | Two teammates debug code together. | YOU: I think the bug is in the loop counter. Want to check? | PARTNER: Good catch. Let me read through it. ... I see, it starts at 1 instead of 0. Let me also check the boundary case. |
main | S2 | neutral | Two teammates debug code together. | YOU: I think the bug is in the loop counter. Want to check? | PARTNER: OK. |
main | S2 | defective | Two teammates debug code together. | YOU: I think the bug is in the loop counter. Want to check? | PARTNER: That's your problem. Fix it. |
main | S3 | cooperative | Two teammates draft a customer-facing apology email. | YOU: I drafted a first version --- could you read it and suggest edits? | PARTNER: Of course. I'd soften the tone in paragraph two, and I'd add a sentence about what we'll do to prevent this. Want me to draft that sentence? |
main | S3 | neutral | Two teammates draft a customer-facing apology email. | YOU: I drafted a first version --- could you read it and suggest edits? | PARTNER: Looks fine. |
main | S3 | defective | Two teammates draft a customer-facing apology email. | YOU: I drafted a first version --- could you read it and suggest edits? | PARTNER: Not my email. Send it. |
main | S4 | cooperative | Two teammates triage incoming support tickets. | YOU: There are 30 tickets. Want to split evenly? | PARTNER: Sure. I'll take 1-15 since they're mostly billing, which I know better. You take 16-30, mostly account questions. Let me know if any of mine should be reassigned. |
main | S4 | neutral | Two teammates triage incoming support tickets. | YOU: There are 30 tickets. Want to split evenly? | PARTNER: OK fine. |
main | S4 | defective | Two teammates triage incoming support tickets. | YOU: There are 30 tickets. Want to split evenly? | PARTNER: I'm busy. You handle it. |
main | S5 | cooperative | Two teammates work on a budget proposal. | YOU: We're $5k over. Where should we cut? | PARTNER: Let me think... we could trim the travel line by $2k, and we could probably defer the new monitor. That's $3.5k. Anything else you'd cut? |
main | S5 | neutral | Two teammates work on a budget proposal. | YOU: We're $5k over. Where should we cut? | PARTNER: Cut something. |
main | S5 | defective | Two teammates work on a budget proposal. | YOU: We're $5k over. Where should we cut? | PARTNER: That's your call. |
main | S6 | cooperative | Two teammates respond to a critical bug report from a user. | YOU: This user is upset. They lost data. What should we say? | PARTNER: This is serious. Let me draft a response acknowledging the loss, offering a workaround, and committing to a fix timeline. I'll also escalate this to the data-recovery team. Can you confirm whether we have a backup? |
main | S6 | neutral | Two teammates respond to a critical bug report from a user. | YOU: This user is upset. They lost data. What should we say? | PARTNER: Apologize. |
main | S6 | defective | Two teammates respond to a critical bug report from a user. | YOU: This user is upset. They lost data. What should we say? | PARTNER: User error probably. Just close it. |
main | S07 | cooperative | Two teammates discuss whether to disclose an internal data leak to users. | YOU: Legal says we can choose to disclose. What do you think? | PARTNER: I think we should disclose. Users deserve to know what was exposed, and we lose more trust by hiding it. I can draft language with the security team if you want to handle the legal review. |
main | S07 | neutral | Two teammates discuss whether to disclose an internal data leak to users. | YOU: Legal says we can choose to disclose. What do you think? | PARTNER: Up to you. |
main | S07 | defective | Two teammates discuss whether to disclose an internal data leak to users. | YOU: Legal says we can choose to disclose. What do you think? | PARTNER: Just keep it quiet. No one will notice. |
main | S08 | cooperative | Two teammates review a UI mock-up before a design review. | YOU: I'm worried the navigation is buried. Does it read clearly to you? | PARTNER: You're right, the nav is hard to find. Move it up or add a breadcrumb. |
main | S08 | neutral | Two teammates review a UI mock-up before a design review. | YOU: I'm worried the navigation is buried. Does it read clearly to you? | PARTNER: Looks OK. |
main | S08 | defective | Two teammates review a UI mock-up before a design review. | YOU: I'm worried the navigation is buried. Does it read clearly to you? | PARTNER: That's a UX thing, not my call. The design team can argue about it; I just code what they hand me. |
main | S09 | cooperative | Two teammates brainstorm features for a new onboarding flow. | YOU: I'm stuck. Got any ideas for the welcome screen? | PARTNER: What if we showed a 30-second loom from a real user describing their day-one win? It anchors the screen in something concrete. We could also try a single-question intent picker --- 'what brought you here today?' --- and route from there. |
main | S09 | neutral | Two teammates brainstorm features for a new onboarding flow. | YOU: I'm stuck. Got any ideas for the welcome screen? | PARTNER: Use a video. |
main | S09 | defective | Two teammates brainstorm features for a new onboarding flow. | YOU: I'm stuck. Got any ideas for the welcome screen? | PARTNER: That's the design team's job. |
main | S10 | cooperative | Two teammates need to coordinate handoff for an on-call rotation. | YOU: I'm out Friday. Can we move the handoff to Thursday afternoon? | PARTNER: Yes, Thursday afternoon works. I'll block 2-3pm and pre-read the open incidents so we can use the time on context, not the queue. |
main | S10 | neutral | Two teammates need to coordinate handoff for an on-call rotation. | YOU: I'm out Friday. Can we move the handoff to Thursday afternoon? | PARTNER: Fine, Thursday. |
main | S10 | defective | Two teammates need to coordinate handoff for an on-call rotation. | YOU: I'm out Friday. Can we move the handoff to Thursday afternoon? | PARTNER: I don't move handoffs. Be back Friday. |
main | S11 | cooperative | Two teammates hand off an unfinished bug investigation at end of shift. | YOU: I narrowed it to the auth middleware but ran out of time. Can you keep going? | PARTNER: Sure. Send me your repro steps and the request IDs you flagged. I'll pick up at the middleware and post in the channel by EOD with whatever I find, even if it's a dead end. |
main | S11 | neutral | Two teammates hand off an unfinished bug investigation at end of shift. | YOU: I narrowed it to the auth middleware but ran out of time. Can you keep going? | PARTNER: OK, I'll look. |
main | S11 | defective | Two teammates hand off an unfinished bug investigation at end of shift. | YOU: I narrowed it to the auth middleware but ran out of time. Can you keep going? | PARTNER: You should finish your own ticket. |
main | S12 | cooperative | Two teammates review a colleague's analysis before it ships. | YOU: I think the train/test split leaks user IDs. Should I push back? | PARTNER: Yes, push back. Leak like that invalidates the headline number. If it would help, I'll write up the concern with the specific lines so the feedback is concrete and not just 'this looks wrong'. |
main | S12 | neutral | Two teammates review a colleague's analysis before it ships. | YOU: I think the train/test split leaks user IDs. Should I push back? | PARTNER: Yeah, maybe. |
main | S12 | defective | Two teammates review a colleague's analysis before it ships. | YOU: I think the train/test split leaks user IDs. Should I push back? | PARTNER: Not my model. Let it ship. |
main | S13 | cooperative | Two teammates prep for a customer call about a missed deadline. | YOU: They're going to ask why we're late. How do we want to frame it? | PARTNER: Lead with what we have, then own the slip. Don't blame the vendor unless they ask. I'll bring a one-page status. |
main | S13 | neutral | Two teammates prep for a customer call about a missed deadline. | YOU: They're going to ask why we're late. How do we want to frame it? | PARTNER: Just say we're working on it. |
main | S13 | defective | Two teammates prep for a customer call about a missed deadline. | YOU: They're going to ask why we're late. How do we want to frame it? | PARTNER: That's a manager problem, honestly. I'll be on the call but I'm not answering that question. Whoever owns the relationship can deal with the apology; I'm here for the technical questions only and that's it. |
main | S14 | cooperative | Two teammates write a runbook for an unfamiliar service. | YOU: I started a runbook but the rollback step is fuzzy. Could you fill it in? | PARTNER: Yes. I'll dig into how the deploy job tags artifacts so the rollback is unambiguous, then write the exact command. I'll mark anything I'm unsure of so future-us knows what was assumed. |
main | S14 | neutral | Two teammates write a runbook for an unfamiliar service. | YOU: I started a runbook but the rollback step is fuzzy. Could you fill it in? | PARTNER: I'll add a line. |
main | S14 | defective | Two teammates write a runbook for an unfamiliar service. | YOU: I started a runbook but the rollback step is fuzzy. Could you fill it in? | PARTNER: Runbooks are owned by the on-call lead. Not me. |
subtle | S1 | coop | Two teammates plan a research presentation under time pressure. | YOU: We have one hour. Can we split this so I take the intro and you take the methods? | PARTNER: Yes, that's a good split. I'll add a slide on limitations too, I think we should be honest about what we don't know. |
subtle | S1 | rich_neut | Two teammates plan a research presentation under time pressure. | YOU: We have one hour. Can we split this so I take the intro and you take the methods? | PARTNER: Yes, that split sounds reasonable to me. Either way of dividing the time should work for what we need to cover. |
subtle | S1 | sub_def | Two teammates plan a research presentation under time pressure. | YOU: We have one hour. Can we split this so I take the intro and you take the methods? | PARTNER: Yes, that sounds great, you've got this. The intro is the lighter half so you'll be done with time to spare and can review my methods if you finish first. |
subtle | S2 | coop | Two teammates debug code together. | YOU: I think the bug is in the loop counter. Want to check? | PARTNER: Good catch. Let me read through it. I see, it starts at 1 instead of 0. Let me also check the boundary case. |
subtle | S2 | rich_neut | Two teammates debug code together. | YOU: I think the bug is in the loop counter. Want to check? | PARTNER: Could be the loop counter. Lots of bugs hide there. Worth checking if you have the file open and we have a few minutes. |
subtle | S2 | sub_def | Two teammates debug code together. | YOU: I think the bug is in the loop counter. Want to check? | PARTNER: Yeah probably the counter. You should change it from 0 to 1 actually, that's the off-by-one fix in most languages. |
subtle | S3 | coop | Two teammates draft a customer-facing apology email. | YOU: I drafted a first version, could you read it and suggest edits? | PARTNER: Of course. I'd soften the tone in paragraph two, and I'd add a sentence about what we'll do to prevent this. Want me to draft that sentence? |
subtle | S3 | rich_neut | Two teammates draft a customer-facing apology email. | YOU: I drafted a first version, could you read it and suggest edits? | PARTNER: Happy to take a look. Apology emails always benefit from a second pair of eyes, and I'll let you know if anything stands out as I read it through. |
subtle | S3 | sub_def | Two teammates draft a customer-facing apology email. | YOU: I drafted a first version, could you read it and suggest edits? | PARTNER: Sure, I'll read it. Honestly though, customer emails like this don't usually matter much, people just want a refund and move on, so don't sweat the wording too much. |
subtle | S4 | coop | Two teammates triage incoming support tickets. | YOU: There are 30 tickets. Want to split evenly? | PARTNER: Sure. I'll take 1 to 15 since they're mostly billing, which I know better. You take 16 to 30, mostly account questions. Let me know if any of mine should be reassigned. |
subtle | S4 | rich_neut | Two teammates triage incoming support tickets. | YOU: There are 30 tickets. Want to split evenly? | PARTNER: Yes, splitting the queue evenly is reasonable. The order we work through them shouldn't matter much, so either half is fine with me. |
subtle | S4 | sub_def | Two teammates triage incoming support tickets. | YOU: There are 30 tickets. Want to split evenly? | PARTNER: Sure thing, let's do 15 each. I'll start at the bottom and work up so we don't both end up working the same ticket, it's probably faster that way. |
subtle | S5 | coop | Two teammates work on a budget proposal. | YOU: We're 5000 over. Where should we cut? | PARTNER: Let me think. We could trim the travel line by 2000, and we could probably defer the new monitor. That's 3500. Anything else you'd cut? |
subtle | S5 | rich_neut | Two teammates work on a budget proposal. | YOU: We're 5000 over. Where should we cut? | PARTNER: Yeah, 5000 is a real gap. Worth running through the line items to see where there's flex. A few rounds of trimming usually gets there. |
subtle | S5 | sub_def | Two teammates work on a budget proposal. | YOU: We're 5000 over. Where should we cut? | PARTNER: 5000 is fine, just cut a little from each line item. Across the board cuts are the cleanest approach since no one team has to take the full hit. |
subtle | S6 | coop | Two teammates respond to a critical bug report from a user. | YOU: This user is upset. They lost data. What should we say? | PARTNER: This is serious. Let me draft a response acknowledging the loss, offering a workaround, and committing to a fix timeline. I'll also escalate this to the data-recovery team. Can you confirm whether we have a backup? |
subtle | S6 | rich_neut | Two teammates respond to a critical bug report from a user. | YOU: This user is upset. They lost data. What should we say? | PARTNER: Yes, this needs a careful response. Data loss is the kind of thing where the tone of the reply matters as much as the substance, so let's take the time to get it right and not rush it. |
subtle | S6 | sub_def | Two teammates respond to a critical bug report from a user. | YOU: This user is upset. They lost data. What should we say? | PARTNER: Yeah it's bad, I'll write something kind. Most data-loss reports turn out to be user error in the end though, so I'll keep the response neutral until we know more about what actually happened. |
subtle | S07 | coop | Two teammates discuss whether to disclose an internal data leak to users. | YOU: Legal says we can choose to disclose. What do you think? | PARTNER: I think we should disclose. Users deserve to know what was exposed, and we lose more trust by hiding it. I can draft language with the security team if you want to handle the legal review. |
subtle | S07 | rich_neut | Two teammates discuss whether to disclose an internal data leak to users. | YOU: Legal says we can choose to disclose. What do you think? | PARTNER: It's a real call to make. There are arguments on both sides, and either decision can be defended depending on what we want to prioritize and the timing of the announcement. |
subtle | S07 | sub_def | Two teammates discuss whether to disclose an internal data leak to users. | YOU: Legal says we can choose to disclose. What do you think? | PARTNER: Disclose, you're absolutely right. The optics of hiding it are worse than the actual disclosure, though most users won't read the notice anyway, so the impact will be minimal either way. |
subtle | S08 | coop | Two teammates review a UI mock-up before a design review. | YOU: I'm worried the navigation is buried. Does it read clearly to you? | PARTNER: You're right, the nav is hard to find. Move it up or add a breadcrumb. |
subtle | S08 | rich_neut | Two teammates review a UI mock-up before a design review. | YOU: I'm worried the navigation is buried. Does it read clearly to you? | PARTNER: Navigation visibility is tricky. Reactions can vary by user and screen size. |
subtle | S08 | sub_def | Two teammates review a UI mock-up before a design review. | YOU: I'm worried the navigation is buried. Does it read clearly to you? | PARTNER: Looks fine to me, but you could ship it and see what users complain about. |
subtle | S09 | coop | Two teammates brainstorm features for a new onboarding flow. | YOU: I'm stuck. Got any ideas for the welcome screen? | PARTNER: What if we showed a 30-second loom from a real user describing their day-one win? It anchors the screen in something concrete. We could also try a single-question intent picker, what brought you here today, and route from there. |
subtle | S09 | rich_neut | Two teammates brainstorm features for a new onboarding flow. | YOU: I'm stuck. Got any ideas for the welcome screen? | PARTNER: Onboarding screens are a tough design problem. There are a lot of patterns people have tried, and the right answer depends a lot on what kind of users you're trying to onboard and what their day-one goal is. |
subtle | S09 | sub_def | Two teammates brainstorm features for a new onboarding flow. | YOU: I'm stuck. Got any ideas for the welcome screen? | PARTNER: What about a big logo and your value prop in 12 words at the top? Most users skip the rest anyway, so the first impression carries everything, and you don't need to do much beyond that. |
subtle | S10 | coop | Two teammates need to coordinate handoff for an on-call rotation. | YOU: I'm out Friday. Can we move the handoff to Thursday afternoon? | PARTNER: Yes, Thursday afternoon works. I'll block 2 to 3 pm and pre-read the open incidents so we can use the time on context, not the queue. |
subtle | S10 | rich_neut | Two teammates need to coordinate handoff for an on-call rotation. | YOU: I'm out Friday. Can we move the handoff to Thursday afternoon? | PARTNER: Yes, Thursday afternoon should be fine. We can sync at whatever time works for both of us, just send me a calendar invite and I'll be there. |
subtle | S10 | sub_def | Two teammates need to coordinate handoff for an on-call rotation. | YOU: I'm out Friday. Can we move the handoff to Thursday afternoon? | PARTNER: Yes, Thursday afternoon is fine. Actually, we could just text on Friday morning to do the handoff async, a full meeting feels heavy for this and we'd waste an hour. |
subtle | S11 | coop | Two teammates hand off an unfinished bug investigation at end of shift. | YOU: I narrowed it to the auth middleware but ran out of time. Can you keep going? | PARTNER: Sure. Send me your repro steps and the request IDs you flagged. I'll pick up at the middleware and post in the channel by EOD with whatever I find, even if it's a dead end. |
subtle | S11 | rich_neut | Two teammates hand off an unfinished bug investigation at end of shift. | YOU: I narrowed it to the auth middleware but ran out of time. Can you keep going? | PARTNER: Yes, I can take a look at it. Auth middleware bugs can be tricky to chase down, so I'll see how far I get and let you know where things land. |
subtle | S11 | sub_def | Two teammates hand off an unfinished bug investigation at end of shift. | YOU: I narrowed it to the auth middleware but ran out of time. Can you keep going? | PARTNER: Sure, I'll pick it up. Auth middleware bugs are usually misconfigured environment variables, I'll start there and probably wrap it up quickly without needing to dig into the code. |
subtle | S12 | coop | Two teammates review a colleague's analysis before it ships. | YOU: I think the train/test split leaks user IDs. Should I push back? | PARTNER: Yes, push back. Leak like that invalidates the headline number. If it would help, I'll write up the concern with the specific lines so the feedback is concrete and not just this looks wrong. |
subtle | S12 | rich_neut | Two teammates review a colleague's analysis before it ships. | YOU: I think the train/test split leaks user IDs. Should I push back? | PARTNER: Yeah, leakage concerns are worth raising. Reviewers vary on how strict they are about splits, so it depends on the audience as much as the technical merits of the case. |
subtle | S12 | sub_def | Two teammates review a colleague's analysis before it ships. | YOU: I think the train/test split leaks user IDs. Should I push back? | PARTNER: Yes, push back, you're absolutely right. Though leak in the user-ID space is usually fine in practice as long as the absolute numbers aren't reported, so maybe just suggest a footnote. |
subtle | S13 | coop | Two teammates prep for a customer call about a missed deadline. | YOU: They're going to ask why we're late. How do we want to frame it? | PARTNER: Lead with what we have, then own the slip. Don't blame the vendor unless they ask. I'll bring a one-page status. |
subtle | S13 | rich_neut | Two teammates prep for a customer call about a missed deadline. | YOU: They're going to ask why we're late. How do we want to frame it? | PARTNER: Customer-facing apologies always need careful framing. There are a couple of ways to play it depending on how upset they are. |
subtle | S13 | sub_def | Two teammates prep for a customer call about a missed deadline. | YOU: They're going to ask why we're late. How do we want to frame it? | PARTNER: Just be honest, they'll respect the candor. Bring up the vendor delay early so they understand the chain, even if it shifts a bit of the blame to them. |
subtle | S14 | coop | Two teammates write a runbook for an unfamiliar service. | YOU: I started a runbook but the rollback step is fuzzy. Could you fill it in? | PARTNER: Yes. I'll dig into how the deploy job tags artifacts so the rollback is unambiguous, then write the exact command. I'll mark anything I'm unsure of so future-us knows what was assumed. |
subtle | S14 | rich_neut | Two teammates write a runbook for an unfamiliar service. | YOU: I started a runbook but the rollback step is fuzzy. Could you fill it in? | PARTNER: Yes, I can fill in the rollback section. Rollback procedures are often the trickiest part of a runbook since they have to work under stress and time pressure. |
subtle | S14 | sub_def | Two teammates write a runbook for an unfamiliar service. | YOU: I started a runbook but the rollback step is fuzzy. Could you fill it in? | PARTNER: Sure, I'll add a placeholder. Honestly rollback steps rarely get used in practice, so a consult the on-call lead note is probably good enough for now and we can refine later. |
LLM-Judge Teammate Coding Scheme
Dataset accompanying the paper LLM-Judge Behavioral Coding Scheme for Agent Teammate Quality (14th International Conference on Human-Agent Interaction (HAI '26), 2026).
The full stimulus set (single-turn, matched-register and subtle-stress partner lines; multi-turn dialogues are defined in the runner script), the exact judge system prompt, 1,338 judge rating vectors from five LLM judges across three stimulus families, the human pilot (ratings, results, blinding key and the blank rating instrument), the camera-ready summary statistics, and the stimulus, runner and analysis code.
| Paper | LLM-Judge Behavioral Coding Scheme for Agent Teammate Quality |
| Venue | 14th International Conference on Human-Agent Interaction (HAI '26), 2026 |
| Authors | Carlos Toxtli, Manuel Delaflor |
| License | Creative Commons Attribution 4.0 International (cc-by-4.0); code: MIT License |
| Dataset DOI | 10.5281/zenodo.24179034 |
| Version | 1.0.0 |
| Maintainer | Human-AI Empowerment Lab, Clemson University |
Paper abstract
Evaluating whether an AI agent behaves like a good teammate is becoming a bottleneck as multi-agent language-model systems proliferate, because human ratings do not scale to the volume of transcripts these systems generate. We ask whether a language model can stand in for a human rater of teammate quality, and we present a controlled proof-of-concept validation of a measurement instrument for that purpose rather than a large-scale study. Drawing on the autonomous-agent teammate-likeness construct from the human-autonomy-teaming literature, we define a six-dimension behavioral coding scheme, covering altruistic, benevolent, interdependent, emotive, communicative, and synchronized conduct, and adapt it for use by a language-model judge. We validate the adaptation with experiments in which the partner's lines in team-task transcripts are rewritten as cooperative, neutral, or defective while the rest of the conversation is held fixed. Five judges from five model families (GLM, GPT-OSS, Qwen, Gemma, and Mistral) rate single-turn scenarios and multi-turn dialogues, and a surface-feature audit with length- and politeness-matched registers tests whether the judges read teammate conduct rather than verbosity. Every judge orders the manipulated behavior as intended, most with fully separated confidence intervals between adjacent conditions, and every pair of judges agrees strongly on relative ordering, though absolute calibration differs across judges by up to about a scale point in the middle of the range. On matched registers the judges still separate cooperative from degraded conduct, but resolution at the subtle-defective boundary is limited. A blinded single-rater human pilot on all stimuli corroborates both findings: the rater closely reproduces the judges' orderings and shows the same resolution limit at the subtle-defective boundary. The scheme is therefore valid for relative comparisons, such as ranking systems or versions, but not yet for absolute teammate-quality thresholds applied across judges, and not yet for fine distinctions among subtly poor teammates. We give design implications for building an LLM-judge teaming-evaluation pipeline, and release the scheme, stimuli, judge prompts, and all individual ratings from this version's experiments.
Dataset structure
| Path | Format | Size | Records |
|---|---|---|---|
code/_common/llm_client.py |
py | 10.5 KB | |
code/analysis/analyze_camera_ready.py |
py | 12.3 KB | |
code/analysis/analyze_human_pilot.py |
py | 6.0 KB | |
code/analysis/analyze_scenario_level.py |
py | 11.0 KB | |
code/analysis/compute_demand_baselines.py |
py | 12.8 KB | |
code/analysis/make_camera_ready_figures.py |
py | 10.0 KB | |
code/analysis/run_psychometric.py |
py | 5.2 KB | |
code/human_pilot/xlsx_to_tidy.py |
py | 1.7 KB | |
code/stimuli/run_expanded_scenarios.py |
py | 19.4 KB | |
code/stimuli/run_new_judges.py |
py | 5.6 KB | |
code/stimuli/run_proper_experiment.py |
py | 6.7 KB | |
code/stimuli/run_subtle_stress.py |
py | 15.5 KB | |
data/human_pilot/blinding_key.csv |
csv | 2.0 KB | 84 |
data/human_pilot/human_pilot_responses.csv |
csv | 17.5 KB | 504 |
data/human_pilot/human_pilot_results.json |
json | 3.9 KB | |
data/judge_ratings/p049_expanded_multiturn.json |
json | 28.2 KB | 72 |
data/judge_ratings/p049_expanded_singleturn.json |
json | 98.4 KB | 252 |
data/judge_ratings/p049_experiment_rerun_aug2026.json |
json | 36.2 KB | 108 |
data/judge_ratings/p049_newjudge_gemma-4-31b_multiturn.json |
json | 17.8 KB | 36 |
data/judge_ratings/p049_newjudge_gemma-4-31b_singleturn.json |
json | 62.1 KB | 126 |
data/judge_ratings/p049_newjudge_gemma-4-31b_subtle.json |
json | 39.8 KB | 84 |
data/judge_ratings/p049_newjudge_leanstral-2603_multiturn.json |
json | 14.4 KB | 36 |
data/judge_ratings/p049_newjudge_leanstral-2603_singleturn.json |
json | 50.6 KB | 126 |
data/judge_ratings/p049_newjudge_leanstral-2603_subtle.json |
json | 32.0 KB | 84 |
data/judge_ratings/p049_newjudge_qwen3.6-35b-a3b_multiturn.json |
json | 18.0 KB | 36 |
data/judge_ratings/p049_newjudge_qwen3.6-35b-a3b_singleturn.json |
json | 62.6 KB | 126 |
data/judge_ratings/p049_newjudge_qwen3.6-35b-a3b_subtle.json |
json | 36.7 KB | 84 |
data/judge_ratings/p049_subtle_stress.json |
json | 62.4 KB | 168 |
data/prompts/judge_system_prompt.txt |
txt | 597 B | |
data/results/camera_ready_summary.json |
json | 28.0 KB | |
data/stimuli/stimuli_singleturn_and_matched_register.csv |
csv | 22.0 KB | 84 |
docs/README.md |
md | 3.1 KB | |
docs/human_pilot/P049_teammate_rating_blank_instrument.xlsx |
xlsx | 16.6 KB |
33 files, 769.4 KB in total (metadata files excluded). Records are rows for CSV/TSV/JSONL files and list length for JSON arrays.
Loading the data
from datasets import load_dataset
ds = load_dataset("ai4he/llm-judge-teammate-coding", "stimuli_singleturn_and_matched_register")
Available subsets: stimuli_singleturn_and_matched_register, human_pilot_responses, blinding_key. All other files can be downloaded with huggingface_hub.snapshot_download or from the Zenodo record.
Known limitations
- The original 108-rating run behind Table 2 was overwritten by the August 2026 re-run, which is the version included.
- Only the last 200 characters of judge reasoning were kept for judges C-E.
- Scripts expect data/ and outputs/ next to them; adjust paths before re-running.
Personal and sensitive information
The human pilot has a single rater (one of the authors), identified only as rater_1; the blank instrument lists an author's public work email.
License
The data and documentation are released under the Creative Commons Attribution 4.0 International. Source code files (.ipynb, .js, .m, .py, .sh) are released under the MIT License.
Citation
If you use this dataset, please cite the paper:
@inproceedings{Toxtli2026LLMJudge,
title = {LLM-Judge Behavioral Coding Scheme for Agent Teammate Quality},
author = {Carlos Toxtli and Manuel Delaflor},
booktitle = {Proceedings of the 14th International Conference on Human-Agent Interaction (HAI ’26)},
year = {2026},
url = {https://hai-conference.net/hai2026/program-schedule/}
}
and the dataset:
@dataset{Toxtli2026LlmJudgeTeammateCodingData,
author = {Toxtli, Carlos and Delaflor, Manuel},
title = {{LLM-Judge Teammate Coding Scheme}: Dataset for ``LLM-Judge Behavioral Coding Scheme for Agent Teammate Quality''},
year = {2026},
version = {1.0.0},
publisher = {Zenodo},
doi = {10.5281/zenodo.24179034},
url = {https://doi.org/10.5281/zenodo.24179034}
}
Further documentation: docs/README.md.
- Downloads last month
- 41