Create query_structure_description.md
Browse files
query_structure_description.md
ADDED
@@ -0,0 +1,49 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
### Documentation: Querying with `**` Anchor Tags
|
2 |
+
|
3 |
+
#### Overview
|
4 |
+
|
5 |
+
This model processes the following data types: `organizations`, `products_and_services`, `topics`, and `classifications`. When querying the model, the developer must pass the query types in a specific format using double asterisks (`**`) to denote emphasis. This format ensures that the model correctly identifies and retrieves the requested data based on the type.
|
6 |
+
|
7 |
+
#### Query Structure for Types
|
8 |
+
|
9 |
+
The structure for querying the model involves passing the type of data in the following format:
|
10 |
+
|
11 |
+
1. **For All Types (Organizations, Products and Services, Topics, Classifications)**:
|
12 |
+
- The type must be **uppercased**.
|
13 |
+
- Any underscores (`_`) in the type name should be replaced with spaces.
|
14 |
+
- The entire type must be wrapped in double asterisks (`**`).
|
15 |
+
- After the formatted type, a newline (`\n`) is inserted, followed by the value from the `anchor` field.
|
16 |
+
- Example query strings:
|
17 |
+
- `**PRODUCTS AND SERVICES**\n{anchor_value}`
|
18 |
+
- `**ORGANIZATIONS**\n{anchor_value}`
|
19 |
+
- `**TOPICS**\n{anchor_value}`
|
20 |
+
- `**CLASSIFICATIONS**\n{anchor_value}`
|
21 |
+
|
22 |
+
#### Query Structure Examples for All Types
|
23 |
+
|
24 |
+
Here’s the complete list of types and how to structure the query for each:
|
25 |
+
|
26 |
+
1. **Products and Services**:
|
27 |
+
- Query format: `**PRODUCTS AND SERVICES**\n{anchor_value}`
|
28 |
+
- Example: `**PRODUCTS AND SERVICES**\nProduct Anchor Text`
|
29 |
+
|
30 |
+
2. **Organizations**:
|
31 |
+
- Query format: `**ORGANIZATIONS**\n{anchor_value}`
|
32 |
+
- Example: `**ORGANIZATIONS**\nOrganization Anchor Text`
|
33 |
+
|
34 |
+
3. **Topics**:
|
35 |
+
- Query format: `**TOPICS**\n{anchor_value}`
|
36 |
+
- Example: `**TOPICS**\nTopic Anchor Text`
|
37 |
+
|
38 |
+
4. **Classifications**:
|
39 |
+
- Query format: `**CLASSIFICATIONS**\n{anchor_value}`
|
40 |
+
- Example: `**CLASSIFICATIONS**\nClassification Anchor Text`
|
41 |
+
|
42 |
+
#### Guidelines for Constructing Queries
|
43 |
+
|
44 |
+
1. **Uppercasing**: Always use uppercase for the type being queried, regardless of the original case in the data.
|
45 |
+
2. **Replacing Underscores**: For types with underscores (`_`), replace them with spaces to ensure proper formatting.
|
46 |
+
3. **Double Asterisks (`**`)**: The type must always be wrapped in double asterisks to emphasize it in the query.
|
47 |
+
4. **Newline for All Types**: Append the `anchor` value after a newline character for all types.
|
48 |
+
|
49 |
+
This ensures consistency and clarity when querying the model for specific data types, allowing accurate data retrieval while maintaining clear formatting.
|