Kagermanov commited on
Commit
4fa9e3b
1 Parent(s): 68e2922

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +16 -4
README.md CHANGED
@@ -189,9 +189,14 @@ Please refer to the documentation of SerpApi's Google Local API and Google Local
189
  <div style="display: flex; justify-content: center;">
190
  <div style="text-align: left;">
191
  <ul style="list-style-position: inside;">
192
- <li>Button text like "Delivery" could be considered <code>service_options</code>. However, this can be easily avoided by checking if a text is in a button in the traditional part of the code. The button text is only used for emergency cases.</li>
193
  <li>The model does not classify the title of a place. This is because the title often contains many elements that can be easily confused with other parts, even for a human eye.</li>
194
  <li>The <code>label</code> key is not covered by the model, as it can be easily handled with traditional code.</li>
 
 
 
 
 
 
195
  <li>In some cases, the model may classify a portion of the <code>description</code> as <code>hours</code> if the description is about operating hours. For example:
196
  <ul style="list-style-type: disc;">
197
  <li><code>"Drive through: Open ⋅ Closes 12 AM"</code>
@@ -202,7 +207,7 @@ Please refer to the documentation of SerpApi's Google Local API and Google Local
202
  </li>
203
  </ul>
204
  </li>
205
- <li>In some cases, the model may classify some <code>description</code> as <code>type</code>. This is because some description do look like type. For Example:
206
  <ul style="list-style-type: circle">
207
  <li><code>"Iconic Seattle-based coffeehouse chain"</code> &rarr; <code>type [Correct Label is description]</code></li>
208
  </ul>
@@ -217,12 +222,19 @@ Please refer to the documentation of SerpApi's Google Local API and Google Local
217
  <li><code>"Takeaway"</code> &rarr; <code>type [Correct Label is service options]</code></li>
218
  </ul>
219
  </li>
220
- <li>In some cases, the model may classify some <code>button text</code> as <code>hours</code>. This is most likely a deficiency in the training dataset, and may be resolved in the coming versions. For Example:
221
  <ul style="list-style-type: circle">
222
  <li><code>"(1.4K)"</code> &rarr; <code>rating [Correct Label is reviews]</code></li>
 
 
 
 
 
 
 
223
  </ul>
224
  </li>
225
- <li>The model may be susceptible to error in one word entries. This is a minority of the cases, and it could be fixed with assurance scores.For Example:
226
  <ul style="list-style-type: circle">
227
  <li><code>"Sushi"</code> &rarr; <code>address(0.984), type(0.0493) [Correct Label is type]</code></li>
228
  <li><code>"Diagorou 4"</code> &rarr; <code>address(0.999) [Correct address in same listing]</code></li>
 
189
  <div style="display: flex; justify-content: center;">
190
  <div style="text-align: left;">
191
  <ul style="list-style-position: inside;">
 
192
  <li>The model does not classify the title of a place. This is because the title often contains many elements that can be easily confused with other parts, even for a human eye.</li>
193
  <li>The <code>label</code> key is not covered by the model, as it can be easily handled with traditional code.</li>
194
+ <li>In some cases, <code>button text</code> could be classified as <code>service options</code> or <code>address</code>. However, this can be easily avoided by checking if a text is in a button in the traditional part of the code. The button text is only used to prevent emergent cases.
195
+ <ul style="list-style-type: circle">
196
+ <li><code>"Delivery"</code> &rarr; <code>service options [Correct Label is button text]</code></li>
197
+ <li><code>"Share"</code> &rarr; <code>address [Correct Label is button text]</code></li>
198
+ </ul>
199
+ </li>
200
  <li>In some cases, the model may classify a portion of the <code>description</code> as <code>hours</code> if the description is about operating hours. For example:
201
  <ul style="list-style-type: disc;">
202
  <li><code>"Drive through: Open ⋅ Closes 12 AM"</code>
 
207
  </li>
208
  </ul>
209
  </li>
210
+ <li>In some cases, the model may classify some <code>description</code> as <code>type</code>. This is because some <code>description</code> do look like <code>type</code>. For Example:
211
  <ul style="list-style-type: circle">
212
  <li><code>"Iconic Seattle-based coffeehouse chain"</code> &rarr; <code>type [Correct Label is description]</code></li>
213
  </ul>
 
222
  <li><code>"Takeaway"</code> &rarr; <code>type [Correct Label is service options]</code></li>
223
  </ul>
224
  </li>
225
+ <li>In some cases, the model may classify some <code>reviews</code> as <code>hours</code> or <code>price</code>. This is most likely a deficiency in the training dataset, and may be resolved in the coming versions. For Example:
226
  <ul style="list-style-type: circle">
227
  <li><code>"(1.4K)"</code> &rarr; <code>rating [Correct Label is reviews]</code></li>
228
+ <li><code>"(1.6K)"</code> &rarr; <code>price [Correct Label is reviews]</code></li>
229
+ </ul>
230
+ </li>
231
+ <li>In some cases, the model may classify some <code>service options</code> as <code>description</code> or <code>type</code>. The reason for the confusion on <code>description</code> is because of a recent change in their categorization in SerpApi keys. The data contains labels prior to that. For Example:
232
+ <ul style="list-style-type: circle">
233
+ <li><code>"On-site services"</code> &rarr; <code>type [Correct Label is service options]</code></li>
234
+ <li><code>"Online appointments"</code> &rarr; <code>description [Correct Label is service options]</code></li>
235
  </ul>
236
  </li>
237
+ <li>The model may be susceptible to error in one word entries. This is a minority of the cases, and it could be fixed with assurance scores. For Example:
238
  <ul style="list-style-type: circle">
239
  <li><code>"Sushi"</code> &rarr; <code>address(0.984), type(0.0493) [Correct Label is type]</code></li>
240
  <li><code>"Diagorou 4"</code> &rarr; <code>address(0.999) [Correct address in same listing]</code></li>