home / pub10

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 adjudicator = "rejected" and app_id = "F1-034"

✎ View and edit SQL

This data as json, CSV (advanced)

verifier_verdict 1

  • rejected 2

run 1

  • b 2

in_final_set 1

  • 0.0 2

app_id 1

  • WeCMDB · 2 ✖

adjudicator 1

  • rejected · 2 ✖
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-034-B041 WeCMDB F1-034 b The system automatically prevents users from adding, modifying or deleting system ENUM types when they try to customize them it cannot be customized adding,modifying or deleting. https://raw.githubusercontent.com/WeBankPartners/we-cmdb/HEAD/wiki/docs/wecmdb_glossary_en.md 04.txt passed rejected Glossary describes enum type constraints, not a user-observable automation or capability.   rejected The glossary entry defines that system enum types are fixed; it is a data-model constraint, not an advertised user capability or automation. 0.0
F1-034-B042 WeCMDB F1-034 b The system automatically prevents users from deleting common ENUM types when they try to delete them but cannot be deleted as it is common which can be used for other CI https://raw.githubusercontent.com/WeBankPartners/we-cmdb/HEAD/wiki/docs/wecmdb_glossary_en.md 04.txt passed rejected Glossary describes enum type constraints, not a user-observable automation or capability.   rejected The glossary entry defines that common enum types cannot be deleted; it is a data-model constraint, not an advertised user capability or automation. 0.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]);
Powered by Datasette · Queries took 901.046ms · Data license: Not yet licensed — internal review only · Data source: Ahmed ElBatanony, Innopolis University