Update README.md
Browse files
README.md
CHANGED
|
@@ -1,3 +1,198 @@
|
|
| 1 |
-
---
|
| 2 |
-
license: cc-by-sa-4.0
|
| 3 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: cc-by-sa-4.0
|
| 3 |
+
language:
|
| 4 |
+
- en
|
| 5 |
+
pretty_name: ServiceNow Incident Search Conversations
|
| 6 |
+
size_categories:
|
| 7 |
+
- n<1K
|
| 8 |
+
task_categories:
|
| 9 |
+
- information-extraction
|
| 10 |
+
- question-answering
|
| 11 |
+
task_ids:
|
| 12 |
+
- text-to-structured
|
| 13 |
+
- tool-use
|
| 14 |
+
- function-calling
|
| 15 |
+
tags:
|
| 16 |
+
- llm
|
| 17 |
+
- tool-calling
|
| 18 |
+
- function-calling
|
| 19 |
+
- servicenow
|
| 20 |
+
- it-service-management
|
| 21 |
+
- itsm
|
| 22 |
+
- enterprise-ai
|
| 23 |
+
- support-automation
|
| 24 |
+
- incident-management
|
| 25 |
+
- structured-output
|
| 26 |
+
- api-generation
|
| 27 |
+
- ai-assistant
|
| 28 |
+
- enterprise-automation
|
| 29 |
+
- rag-compatible
|
| 30 |
+
- synthetic-data
|
| 31 |
+
- prompt-engineering
|
| 32 |
+
- dataset-generation
|
| 33 |
+
- conversational-ai
|
| 34 |
+
- devops
|
| 35 |
+
- helpdesk
|
| 36 |
+
annotations_creators:
|
| 37 |
+
- machine-generated
|
| 38 |
+
language_creators:
|
| 39 |
+
- machine-generated
|
| 40 |
+
multilinguality:
|
| 41 |
+
- monolingual
|
| 42 |
+
source_datasets:
|
| 43 |
+
- synthetic
|
| 44 |
+
domain:
|
| 45 |
+
- enterprise
|
| 46 |
+
- information-technology
|
| 47 |
+
- customer-support
|
| 48 |
+
- devops
|
| 49 |
+
task_domain:
|
| 50 |
+
- enterprise-ai
|
| 51 |
+
- workflow-automation
|
| 52 |
+
author:
|
| 53 |
+
- C. J. Jones
|
| 54 |
+
dataset_type:
|
| 55 |
+
- conversational
|
| 56 |
+
- structured-query
|
| 57 |
+
version: 1.0.0
|
| 58 |
+
---
|
| 59 |
+
This dataset contains structured User → Bot conversations demonstrating how a natural language request can be translated into a structured ServiceNow incident search API call.
|
| 60 |
+
|
| 61 |
+
Each record consists of a user requesting incident data from an IT service management system and a bot responding with a JSON query specification compatible with the ServiceNow Table API.
|
| 62 |
+
|
| 63 |
+
The dataset is designed for training and evaluating LLM tool-use capabilities, specifically:
|
| 64 |
+
|
| 65 |
+
Natural language → API query translation
|
| 66 |
+
|
| 67 |
+
Incident ticket search automation
|
| 68 |
+
|
| 69 |
+
IT service desk assistant systems
|
| 70 |
+
|
| 71 |
+
Enterprise workflow copilots
|
| 72 |
+
|
| 73 |
+
Retrieval query generation
|
| 74 |
+
|
| 75 |
+
The bot responses strictly follow a structured schema that represents a ServiceNow incident table search operation.
|
| 76 |
+
|
| 77 |
+
This dataset preview includes 10 example conversation pairs.
|
| 78 |
+
|
| 79 |
+
Supported Tasks
|
| 80 |
+
|
| 81 |
+
tool-use
|
| 82 |
+
|
| 83 |
+
function calling
|
| 84 |
+
|
| 85 |
+
information extraction
|
| 86 |
+
|
| 87 |
+
enterprise automation
|
| 88 |
+
|
| 89 |
+
natural language query translation
|
| 90 |
+
|
| 91 |
+
retrieval query generation
|
| 92 |
+
|
| 93 |
+
Languages
|
| 94 |
+
|
| 95 |
+
English
|
| 96 |
+
|
| 97 |
+
Dataset Structure
|
| 98 |
+
|
| 99 |
+
Each sample contains two fields:
|
| 100 |
+
|
| 101 |
+
{
|
| 102 |
+
"user": string,
|
| 103 |
+
"bot": string
|
| 104 |
+
}
|
| 105 |
+
Field Descriptions
|
| 106 |
+
Field Description
|
| 107 |
+
user Natural language request asking for incident or ticket history
|
| 108 |
+
bot Structured JSON tool call specifying the ServiceNow search parameters
|
| 109 |
+
Example
|
| 110 |
+
User: Could you get trouble tickets that mention API integration failures regarding Seattle office staff ranking 2 for post-mortem review.
|
| 111 |
+
|
| 112 |
+
Bot:
|
| 113 |
+
{
|
| 114 |
+
"action": "servicenow.table.search",
|
| 115 |
+
"parameters": {
|
| 116 |
+
"tableName": "incident",
|
| 117 |
+
"query": {
|
| 118 |
+
"short_description": "CONTAINS: API integration failures",
|
| 119 |
+
"location": "Seattle office",
|
| 120 |
+
"priority": "2"
|
| 121 |
+
},
|
| 122 |
+
"sysparm_limit": "21",
|
| 123 |
+
"sysparm_fields": "number,short_description,description,priority,sys_created_on,assignment_group,location,state",
|
| 124 |
+
"sysparm_display_value": "false"
|
| 125 |
+
}
|
| 126 |
+
}
|
| 127 |
+
Data Instances
|
| 128 |
+
|
| 129 |
+
Example dataset record:
|
| 130 |
+
|
| 131 |
+
{
|
| 132 |
+
"user": "Locate employee reports about wireless access point outages in Marketing group for Sao Paulo office region Critical priority incidents for compliance purposes.",
|
| 133 |
+
"bot": "{ \"action\": \"servicenow.table.search\", \"parameters\": { \"tableName\": \"incident\", \"query\": { \"description\": \"CONTAINS: wireless access point outages\", \"assignment_group\": \"Marketing\", \"location\": \"Sao Paulo office\", \"priority\": \"1\" }, \"sysparm_limit\": \"39\", \"sysparm_fields\": \"number,short_description,description,priority,sys_created_on,assignment_group,location,state\", \"sysparm_display_value\": \"true\" }}"
|
| 134 |
+
}
|
| 135 |
+
Dataset Creation
|
| 136 |
+
Source
|
| 137 |
+
|
| 138 |
+
The conversations were synthetically generated using programmatic generation techniques designed to simulate realistic enterprise IT service desk queries.
|
| 139 |
+
|
| 140 |
+
Generation introduces variation across:
|
| 141 |
+
|
| 142 |
+
issue categories
|
| 143 |
+
|
| 144 |
+
office locations
|
| 145 |
+
|
| 146 |
+
organizational departments
|
| 147 |
+
|
| 148 |
+
priority levels
|
| 149 |
+
|
| 150 |
+
request phrasing
|
| 151 |
+
|
| 152 |
+
reporting contexts
|
| 153 |
+
|
| 154 |
+
Example issue types include:
|
| 155 |
+
|
| 156 |
+
API integration failures
|
| 157 |
+
|
| 158 |
+
wireless access point outages
|
| 159 |
+
|
| 160 |
+
network switch port errors
|
| 161 |
+
|
| 162 |
+
single sign-on errors
|
| 163 |
+
|
| 164 |
+
firewall configuration errors
|
| 165 |
+
|
| 166 |
+
power supply failures
|
| 167 |
+
|
| 168 |
+
password reset requests
|
| 169 |
+
|
| 170 |
+
email delivery issues
|
| 171 |
+
|
| 172 |
+
Generation Strategy
|
| 173 |
+
|
| 174 |
+
Records were generated to maximize variation in:
|
| 175 |
+
|
| 176 |
+
user intent phrasing
|
| 177 |
+
|
| 178 |
+
department references
|
| 179 |
+
|
| 180 |
+
location mentions
|
| 181 |
+
|
| 182 |
+
priority terminology
|
| 183 |
+
|
| 184 |
+
reporting context
|
| 185 |
+
|
| 186 |
+
The output schema enforces consistent structure compatible with ServiceNow incident table queries.
|
| 187 |
+
|
| 188 |
+
Intended Use
|
| 189 |
+
|
| 190 |
+
This dataset is intended for:
|
| 191 |
+
|
| 192 |
+
training LLM agents that interact with enterprise systems
|
| 193 |
+
|
| 194 |
+
benchmarking tool-calling accuracy
|
| 195 |
+
|
| 196 |
+
developing AI service desk assistants
|
| 197 |
+
|
| 198 |
+
research on structured query generation
|