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

1 row where app_id = "F1-002", in_final_set = "1.0" and verifier_verdict = "rejected"

✎ View and edit SQL

This data as json, CSV (advanced)

verifier_verdict 1

  • rejected · 1 ✖

run 1

  • b 1

in_final_set 1

app_id 1

  • It's a Plan · 1 ✖

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
F1-002-B052 It's a Plan F1-002 b The system lets a user set an owner, a priority, a target date and a health status on an initiative It has an owner, a priority, a target date and a health status, and its progress counts the issues under it by state. https://itsaplan.dev/features/initiatives 05.txt passed rejected duplicate of F1-002-A030   corrected The health status is advertised separately in the sources and is absent from A030, so only that part is not a duplicate. 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]);