Search

Pramata Prompt Parameters

 

This guide will help you understand how to use Pramata's Prompt Parameters effectively when working with GenAI prompts. Prompt Parameters allow you to customize prompt content dynamically based on user input, system data, or document context.

 

Understanding Prompt Parameters

Prompt Parameters are placeholders within a prompt that get replaced with specific values at runtime. Unlike Prompt Variables, which help determine the overall context sent to the LLM, Prompt Parameters are directly substituted in the text wherever they appear. This allows for more flexible and targeted prompt construction.

 

Prompt Parameter Overview

Here are the key Prompt Parameters used in the Pramata Platform, each with a short definition:

  • {{#clause}} — Replaces the placeholder with the name of a target clause.
  • {{#redline_guidelines}} — Inserts redline guidance or policy language into the prompt.
  • {{#original_para_text}} — Inserts the original paragraph or clause text from a contract.
  • {{#party_perspective}} — Indicates the perspective of a party involved in the contract.
  • {{#our_entities}} — Lists recognized entity names associated with the customer/tenant.
  • {{#terms}} — Inserts a list of terms or clauses to be analyzed.
  • {{#field_name}} — Substitutes values from form fields directly into prompts.
  • {{#auto_populate_form}} — Instructs the LLM to generate JSON objects for automated form field population based on contract data.

 

{{#clause}}

Inserts the clause name passed to the prompt

Example:

Prompt: Set TargetClause to: {{#clause}}
Parameter Passed: Assignment
Transformed: Set TargetClause to: Assignment

Agent Processing Impact: If an agent prompt uses {{#clause}}, the agent is called once per clause. If not, it's called only once regardless of the number of selected clauses.

Playbook Impact: When used with Playbook prompt variables, only guidelines for the specific clause are passed—not the full Playbook.

Key Term Impact ({{kt}} / {{kt+}}): Only contracts with the specified clause are passed in. Others are excluded.

 

{{#redline_guidelines}}

Replaces the tag with specific redlining instructions.

Example:

Prompt: Set RedlineGuidlines to: {{#redline_guidelines}}
Parameter Passed: No assignments allowed.
Transformed: Set RedlineGuidlines to: No assignments allowed.

 

{{#party_perspective}}

Replaces legacy {{PARTY}} variable; indicates the party’s role or identity.

Example:

Prompt: Set PartyPerspective to: {{#party_perspective}}
Parameter Passed: Acme, Inc.
Transformed: Set PartyPerspective to: Acme, Inc.

 

{{#our_entities}}

Definition: Lists known entity names for the customer/tenant.

Example:

Prompt: IF a contracting entity matches one of {{#our_entities}} THEN set PartyPerspective to the contracting entity
Parameter Passed: Acme, Acme Inc., Acme Corporation
Transformed: IF a contracting entity matches one of Acme, Acme Inc., Acme Corporation THEN set PartyPerspective to the contracting entity

 

{{#terms}}

Used to pass in a list of clauses or key terms.

Example:

Prompt: Set Terms to: {{#terms}}
Parameter Passed: Assignment Notice Period, Consent Required
Transformed: Set Terms to: Assignment Notice Period, Consent Required

 

{{#field_name}}

Used in form assist agents for direct field value substitution.

Example:

Prompt: Generate a contract summary for {{#counterparty_name}} with effective date {{#effective_date}}
Parameters Passed: Acme Corporation, 2025-05-01
Transformed: Generate a contract summary for Acme Corporation with effective date 2025-05-01

Use Cases:

  • Substituting individual form field values
  • Creating dynamic summaries or reports
  • Building targeted prompts from structured form input

 

{{#auto_populate_form}}

Instructs the LLM to generate a JSON object for automatically populating form fields based on the fields chosen in the form. This parameter is completely optional, as sometimes LLM fails to generate the Form response, so adding this ensures the LLM generates the form response in the output.

Example:

Prompt: Generate a contract request form with the following details: {{#auto_populate_form}}
Parameter Passed: [Generate form_response with keys: Counter_party, amount]
Transformed: Generate a contract request form with the following details: [Generate form_response with keys: Counter_party, amount]

Use Cases:

  • Automated form field population
  • Intelligent form completion
  • Reducing manual data entry
  • Ensuring consistency in form data