Hide awareness_presentation from the review view
Browse files
README.md
CHANGED
|
@@ -27,7 +27,6 @@ configs:
|
|
| 27 |
- industry
|
| 28 |
- price_point
|
| 29 |
- completeness
|
| 30 |
-
- awareness_presentation
|
| 31 |
- approval
|
| 32 |
dataset_info:
|
| 33 |
features:
|
|
@@ -57,8 +56,6 @@ dataset_info:
|
|
| 57 |
dtype: string
|
| 58 |
- name: completeness
|
| 59 |
dtype: string
|
| 60 |
-
- name: awareness_presentation
|
| 61 |
-
dtype: string
|
| 62 |
- name: approval
|
| 63 |
dtype: bool
|
| 64 |
---
|
|
@@ -88,7 +85,7 @@ Review the generated marketing requests and record approval directly in the data
|
|
| 88 |
|
| 89 |
- Does **user_text** sound like a believable request and ask for the correct deliverable?
|
| 90 |
- Are product facts, pricing, audience, evidence, and prohibitions preserved without invented details?
|
| 91 |
-
- Does the awareness stage match the information provided? A blank awareness field
|
| 92 |
- If **completeness** is `needs_clarification`, does the request preserve the unresolved choices instead of inventing answers? Missing information is intentional in some examples.
|
| 93 |
|
| 94 |
## Tips
|
|
|
|
| 27 |
- industry
|
| 28 |
- price_point
|
| 29 |
- completeness
|
|
|
|
| 30 |
- approval
|
| 31 |
dataset_info:
|
| 32 |
features:
|
|
|
|
| 56 |
dtype: string
|
| 57 |
- name: completeness
|
| 58 |
dtype: string
|
|
|
|
|
|
|
| 59 |
- name: approval
|
| 60 |
dtype: bool
|
| 61 |
---
|
|
|
|
| 85 |
|
| 86 |
- Does **user_text** sound like a believable request and ask for the correct deliverable?
|
| 87 |
- Are product facts, pricing, audience, evidence, and prohibitions preserved without invented details?
|
| 88 |
+
- Does the awareness stage match the information provided? A blank awareness field is expected when the request does not name a stage.
|
| 89 |
- If **completeness** is `needs_clarification`, does the request preserve the unresolved choices instead of inventing answers? Missing information is intentional in some examples.
|
| 90 |
|
| 91 |
## Tips
|