features
Data license: Not yet licensed — internal review only · Data source: Ahmed ElBatanony, Innopolis University
- form
- user-action = 'The system lets …'; automation = 'The system automatically …'.
- found_by
- Which blind run's wording was kept (the other run may also have found it), or verifier/adjudicator for added capabilities.
- verification
- confirmed by the verifier; corrected (reworded); or added (missed by both runs).
- pipeline_id
- Link to the full pipeline record of this statement.
- source_sha256
- sha256 of the archived plain text the excerpt was checked against.
- audited
- 1 if the row is in the 150-row blind audit sample.
- audit_correct
- Blind auditor's overall verdict (1 = acceptable as is).
2 rows where app_id = "F2-043" and verification = "corrected" sorted by feature_id
This data as json, CSV (advanced)
form 2
verification 1
- corrected · 2 ✖
audit_correct 1
- 1.0 1
app_id 1
- ServiceNow IT Service Management · 2 ✖
| feature_id ▼ | app_id | statement | form | excerpt | source_url | source_file | source_sha256 | found_by | found_by_runs | verification | pipeline_id | audited | audit_correct | audit_note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| F2-043-S054 | ServiceNow IT Service Management F2-043 | The system automatically triggers email notifications or scripts when an incident has no updates over a specified time | automation | 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 | 694831e41cd3978ec15d23bf46a0c9d07ca346fcbed57e04cfc56b8e8744969a | extract-a | both | corrected | The system automatically generates an event to prevent incidents from going unnoticed F2-043-A057 | 0.0 | ||
| F2-043-S152 | ServiceNow IT Service Management F2-043 | The system lets a user email a change record, with the requester and the assignee prefilled as recipients | user-action | 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 | 0cf9cdd1162a5807230168f75d44b96ce7b8a272d98d61017704eda0a74a67f5 | extract-b | b | corrected | The system automatically populates the requester and the assignee as recipients when a user emails a change record F2-043-B161 | 1.0 | 1.0 | Emailing the change record is in the surrounding sentence, excerpt only covers recipients. |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [features] ([feature_id] TEXT PRIMARY KEY, [app_id] TEXT, [statement] TEXT, [form] TEXT, [excerpt] TEXT, [source_url] TEXT, [source_file] TEXT, [source_sha256] TEXT, [found_by] TEXT, [found_by_runs] TEXT, [verification] TEXT, [pipeline_id] TEXT, [audited] REAL, [audit_correct] REAL, [audit_note] TEXT, FOREIGN KEY ([app_id]) REFERENCES apps(app_id), FOREIGN KEY ([pipeline_id]) REFERENCES candidates(candidate_id)); CREATE INDEX [idx_features_app_id] ON [features]([app_id]); CREATE INDEX [idx_features_verification] ON [features]([verification]); CREATE INDEX [idx_features_form] ON [features]([form]); CREATE INDEX [idx_features_found_by] ON [features]([found_by]);