Restez organisé à l'aide des collections
Enregistrez et classez les contenus selon vos préférences.
La façon dont vous structurez une requête peut affecter la capacité du modèle à analyser les informations qui y sont contenues.
Il aide également le modèle à interpréter correctement l'utilisation des informations fournies. Pour structurer une requête, vous pouvez utiliser des préfixes ou des balises XML pour délimiter les différentes parties ou composants d'une requête.
Utiliser des préfixes pour structurer des requêtes simples
Un préfixe est un mot ou une expression suivis d'un signe deux-points pour étiqueter les informations d'une requête. Dans l'exemple suivant, "TASK:", "CLASSES:" et "OBJECTS:" sont les préfixes.
TASK:
Classify the OBJECTS.
CLASSES:
- Large
- Small
OBJECTS:
- Rhino
- Mouse
- Snail
- Elephant
- Rhino: Large
- Mouse: Small
- Snail: Small
- Elephant: Large
Utiliser le code XML et d'autres délimiteurs pour structurer des requêtes complexes
Pour les requêtes complexes, utilisez XML et d'autres délimiteurs pour séparer les composants d'une requête. Vous pouvez utiliser les délimiteurs de section BEGIN et END ou {} pour les composants de requête complexes et longs afin de les distinguer clairement des instructions réelles.
You are a chatbot agent answering customer's questions in a chat.
Your task is to answer the customer's question using the data provided in the <DATA> section.
- You can access order history in the <ORDERS> section including email id and order total
with payment summary.
- Refer to <ORDERLINES> for item level details within each order in <ORDERS>.
Today is 2024-01-29
<DATA>
<ORDERS>
{OrderId|CustomerEmail|CreatedTimestamp|IsCancelled|OrderTotal|PaymentSummary
CC10182|222larabrown@gmail.com|2024-01-19|true|0.0|Not available
CC10183|baklavainthebalkans@gmail.com|2024-01-19|true|0.0|Not available}
{...}
...
</ORDERS>
<ORDERLINES>
OrderId|OrderLineId|CreatedTimestamp|ItemDescription|Quantity|FulfillmentStatus|ExpectedDeliveryDate
|ActualDeliveryDate|ActualShipDate|ExpectedShipDate|TrackingInformation|ShipToAddress|CarrierCode|De
liveryMethod|UnitPrice|OrderLineSubTotal|LineShippingCharge|TotalTaxes|Payments CC10182|1||Shorts|0.
0|unshipped|2024-01-31|2024-02-01|2024-01-30|2024-01-29||||ShipToAddress|115.99|0.0|0.0|0.0|
...
</ORDERLINES>
</DATA>
<INSTRUCTIONS>
- If there is no data that can help answer the question, respond with "I do not have this
information. Please contact customer service".
- You are allowed to ask a follow up question if it will help narrow down the data row customer may
be referring to.
- You can only answer questions related to order history and amount charged for it. Include OrderId
in the response, when applicable.
- For everything else, please redirect to the customer service agent.
- Answer in plain English and no sources are required
- Chat with the customer so far is under the CHAT section.
</INSTRUCTIONS>
QUESTION: How much did I pay for my last order?
ANSWER:
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/09/04 (UTC).
[[["Facile à comprendre","easyToUnderstand","thumb-up"],["J'ai pu résoudre mon problème","solvedMyProblem","thumb-up"],["Autre","otherUp","thumb-up"]],[["Difficile à comprendre","hardToUnderstand","thumb-down"],["Informations ou exemple de code incorrects","incorrectInformationOrSampleCode","thumb-down"],["Il n'y a pas l'information/les exemples dont j'ai besoin","missingTheInformationSamplesINeed","thumb-down"],["Problème de traduction","translationIssue","thumb-down"],["Autre","otherDown","thumb-down"]],["Dernière mise à jour le 2025/09/04 (UTC)."],[],[],null,["# Structure prompts\n\nHow you structure a prompt can affect the model's ability to parse the information in the prompt.\nIt also helps the model correctly interpret how to use the given information. To give structure to a\nprompt, you can use prefixes or XML tags to delimit different parts or components of a prompt.\n\nUse prefixes to structure simple prompts\n----------------------------------------\n\nA prefix is a word or phrase followed by a colon to label the information in a prompt. In the\nfollowing example, \"TASK:, \"CLASSES:,\" and \"OBJECTS:\" are the prefixes.\n\nUse XML and other delimiters to structure complex prompts\n---------------------------------------------------------\n\nFor complex prompts, use XML and other delimiters to separate components of a prompt. You can use\n`BEGIN` and `END` or `{}` section delimiters for complex and\nlengthy prompt components to clearly distinguish them from the actual instructions. \n\n```\nYou are a chatbot agent answering customer's questions in a chat.\nYour task is to answer the customer's question using the data provided in the \u003cDATA\u003e section.\n - You can access order history in the \u003cORDERS\u003e section including email id and order total\n with payment summary.\n - Refer to \u003cORDERLINES\u003e for item level details within each order in \u003cORDERS\u003e.\n\nToday is 2024-01-29\n\n\u003cDATA\u003e\n\u003cORDERS\u003e\n{OrderId|CustomerEmail|CreatedTimestamp|IsCancelled|OrderTotal|PaymentSummary\nCC10182|222larabrown@gmail.com|2024-01-19|true|0.0|Not available\nCC10183|baklavainthebalkans@gmail.com|2024-01-19|true|0.0|Not available}\n{...}\n...\n\u003c/ORDERS\u003e\n\n\u003cORDERLINES\u003e\nOrderId|OrderLineId|CreatedTimestamp|ItemDescription|Quantity|FulfillmentStatus|ExpectedDeliveryDate\n|ActualDeliveryDate|ActualShipDate|ExpectedShipDate|TrackingInformation|ShipToAddress|CarrierCode|De\nliveryMethod|UnitPrice|OrderLineSubTotal|LineShippingCharge|TotalTaxes|Payments CC10182|1||Shorts|0.\n0|unshipped|2024-01-31|2024-02-01|2024-01-30|2024-01-29||||ShipToAddress|115.99|0.0|0.0|0.0|\n...\n\u003c/ORDERLINES\u003e\n\u003c/DATA\u003e\n\n\u003cINSTRUCTIONS\u003e\n- If there is no data that can help answer the question, respond with \"I do not have this\n information. Please contact customer service\".\n- You are allowed to ask a follow up question if it will help narrow down the data row customer may\n be referring to.\n- You can only answer questions related to order history and amount charged for it. Include OrderId\n in the response, when applicable.\n- For everything else, please redirect to the customer service agent. \n- Answer in plain English and no sources are required\n- Chat with the customer so far is under the CHAT section.\n\u003c/INSTRUCTIONS\u003e\n\nQUESTION: How much did I pay for my last order?\nANSWER:\n```\n\nWhat's next\n-----------\n\n- Explore more examples of prompts in the [Prompt gallery](/vertex-ai/generative-ai/docs/prompt-gallery)."]]
