⬆
Upload Data
Get to know how to upload data to train/test model
You can check the following data in the Dashboard data area.
- Data uploaded directly via File uploading
- Data uploaded directly through Sentence input
There are three upload methods, but they can all be browsed in one data area on Dashboard page.
GNB > Dashboard
When uploading a file, you can choose whether to use the data as training or test data in advance. By selecting the Train/Test option and uploading the file, the dashboard will be presented with the toggle on for each option.
If you select the RANDOM option when uploading a file, you can enter a percentage (%). Among the data in the file, the percentage entered (e.g. 20%) is randomly set as test data, and the remaining percentage (e.g. 80%) is set as training data.
GNB > Dashboard (& Inference) > Upload Phrases dialog
After the upload is complete, you can check the Train/Test setting (toggle) status of each data in the dashboard.
You can upload JSON, TXT/TSV, and XLSX files.
GNB > Dashboard (& Inference) > Upload Phrases dialog
{
{'text': 'hello Mom', "review_sentiments": [{"category":"만족도", "sentiment":'1'}]},
{'text': 'hello kid', "review_sentiments": [{"category":"delicious", "sentiment":'1'}]},
{'text': "what's dinner?",},
{'text': 'chicken dinner!',}
}
- If category tags exist, a header must be included (as in the first example).
- The text (classification target) must be located at the very beginning.
- If category tags do not exist, the header can be omitted (as in the second example).
- The data should be separated by tabs.
REVIEW\t Satisfaction\t Price
Very tasty and affordable\t2\t2
I would like to eat again later\t2\t1
Very tasty and affordable
I would like to eat again later
- The order of the columns does not matter.
- The sentiment must be one of the following values: -2, -1, 0, 1, or 2.
|REVIEW| category |sentiment|
|------|----------|---------|
|hello | PRICE | 1 |
|myhome| LENGTH | 2 |
|dinner| MATERIAL| -1 |
| REVIEW |
|--------------|
|hello friends!|
{
{'text': 'hello Mom',
"entities":[{"tag": {"name": "family"}, "start": 6, "end": 9, "token": "Mom"}]},
{'text': 'hello kid'}
}
- Column names must be specified. The order of column names does not matter.
- The column names are ["PHRASE", "TOKEN", "START", "END", "TAG", "NO"]
- The order of column names does not matter.
- 'NO' is an optional column.
|PHRASE. |TOKEN|START|END|TAG. |NO|
|-------------|-----|-----|---|----------------------|--|
|hello mom. |mom | 6 | 8 |{'name':'family'} |2 |
{
{'text': 'hello Mom', 'intent': {'name': 'good'}},
{'text': 'hello kid'}
}
- There are no column names.
- The data can be in either the [text] or [intent, text] format.
- If intent is present, it should be placed before text.
- Both of the following formats are valid:
- GOOD So GoodBAD So BadSo GoodSo Bad
- There are no specific column names required.
- It can be either in the form of [text] or [intent, text].
- Both examples below are valid.
|GOOD|hello mom!!|
|GOOD|hello dad!!|
|BAD|get out bob!!|
|hello mom!!|
|hello dad!!|
{
{'text': 'hello Mom!!',
'tree_classes': [
{'category': 'Large Category', 'value': 'Mom'},
{'category': 'Medium Category', 'value': 'Woman'},
{'category': 'Small Category', 'value': '50'}
]
}
{'text': 'hello kid'},
}
- If there are category tags, there must be a header (first example).
- The text (classification target) must be located at the very beginning.
- If there are no category tags, the header can be omitted (second example).
- The data is separated by a tab.
TREE\t Satisfaction\t Price
There are a lot of people \t1\t1
it's delicious even though I have to wait a bit. \t2\t2
There are a lot of people
it's delicious even though I have to wait a bit.
- Column names must exist and the following order must be followed:
- TEXT - Large category - Medium category - Small category
|TEXT | Large Category | Medium Category | Small Category. |
|hello Mom. | 1 | 2 | 3. |
|hello kid. | Company | Engineer | New Employee. |
Last modified 5mo ago