A partir de 29 de abril de 2025, os modelos Gemini 1.5 Pro e Gemini 1.5 Flash não estarão disponíveis em projetos que não os usaram antes, incluindo novos projetos. Para mais detalhes, consulte Versões e ciclo de vida do modelo.
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
A estrutura de um comando pode afetar a capacidade do modelo de analisar as informações contidas no comando.
Ela também ajuda a interpretar corretamente como usar as informações apresentadas. Para dar estrutura a um comando, use prefixos ou tags XML para delimitar diferentes partes ou componentes dele.
Usar prefixos para estruturar comandos simples
Um prefixo é uma palavra ou frase seguida por dois-pontos para rotular as informações em um comando. No exemplo a seguir, "TASK:", "CLASSES:" e "OBJECTS:" são os prefixos.
TASK:
Classify the OBJECTS.
CLASSES:
- Large
- Small
OBJECTS:
- Rhino
- Mouse
- Snail
- Elephant
- Rhino: Large
- Mouse: Small
- Snail: Small
- Elephant: Large
Usar XML e outros delimitadores para estruturar comandos complexos
Para comandos complexos, use XML e outros delimitadores para separar os componentes de um comando. É possível usar delimitadores de seção BEGIN e END ou {} para componentes de comandos complexos e longos a fim de diferenciá-los com clareza das instruções reais.
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:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 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)."]]
