candidates

Every statement both blind runs produced (3,819), with its full trail: script check → verifier verdict and reason → adjudicator ruling and reason → whether it is in the final set. Most rejections are duplicates between the two runs.

Data license: Not yet licensed — internal review only · Data source: Ahmed ElBatanony, Innopolis University

2 rows where app_id = "F2-043" and verifier_verdict = "corrected"

✎ View and edit SQL

This data as json, CSV (advanced)

run 2

verifier_verdict 1

  • corrected · 2 ✖

in_final_set 1

app_id 1

  • ServiceNow IT Service Management · 2 ✖

adjudicator 1

candidate_id ▼ app_id run statement excerpt source_url source_file script_check verifier_verdict verifier_reason verifier_correction adjudicator adjudicator_reason in_final_set
F2-043-A057 ServiceNow IT Service Management F2-043 a The system automatically generates an event to prevent incidents from going unnoticed The inactivity monitor generates an event to prevent incidents from going unnoticed https://www.servicenow.com/docs/api/khub/maps/eH2O6EPUpf09wX0~2cZBFg/topics/Uc8KCF0LjG~p2cz7LcOYiw/content 10.txt passed corrected Original was vague about the trigger and effect. The system automatically triggers email notifications or scripts when an incident has no updates over a specified time corrected The source (10.txt line 24) states the trigger and effect that the original statement left vague. 1.0
F2-043-B161 ServiceNow IT Service Management F2-043 b The system automatically populates the requester and the assignee as recipients when a user emails a change record Both the user who requested the change and the user who is assigned to the change are automatically populated in the list of recipients. https://www.servicenow.com/docs/api/khub/maps/eH2O6EPUpf09wX0~2cZBFg/topics/uXk8LEj8iwoJoS8~QkyrIA/content 21.txt passed corrected Source describes a user-initiated email action, not an automatic population on its own. The system lets a user email a change record, with the requester and the assignee prefilled as recipients corrected The source describes a user-initiated email action with prefilled recipients, not a standalone automation. 1.0

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [candidates] ([candidate_id] TEXT PRIMARY KEY, [app_id] TEXT, [run] TEXT, [statement] TEXT, [excerpt] TEXT, [source_url] TEXT, [source_file] TEXT, [script_check] TEXT, [verifier_verdict] TEXT, [verifier_reason] TEXT, [verifier_correction] TEXT, [adjudicator] TEXT, [adjudicator_reason] TEXT, [in_final_set] REAL, FOREIGN KEY ([app_id]) REFERENCES apps(app_id));
CREATE INDEX [idx_candidates_app_id] ON [candidates]([app_id]);
CREATE INDEX [idx_candidates_run] ON [candidates]([run]);
CREATE INDEX [idx_candidates_verifier_verdict] ON [candidates]([verifier_verdict]);
CREATE INDEX [idx_candidates_adjudicator] ON [candidates]([adjudicator]);