Dgreenwood at 21:43, 27 August 2025

2025-08-27T21:43:54Z

← Older revision		Revision as of 16:43, 27 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}

Randallkinard at 19:39, 21 November 2024

2024-11-21T19:39:46Z

← Older revision		Revision as of 14:39, 21 November 2024
Line 177:		Line 177:

	[[Image:GPT Integration 048.png]]		[[Image:GPT Integration 048.png]]

	~~== Glossary ==~~
	~~<u><big>'''Data Field'''</big></u>: {{#lst:Glossary\|Data Field}}~~

	~~<u><big>'''Data Model'''</big></u>: {{#lst:Glossary\|Data Model}}~~

	~~<u><big>'''Execute'''</big></u>: {{#lst:Glossary\|Execute}}~~

	~~<u><big>'''GPT Complete'''</big></u>: {{#lst:Glossary\|GPT Complete}}~~

	~~<u><big>'''GPT Integration'''</big></u>: {{#lst:Glossary\|GPT Integration}}~~

	~~<u><big>'''GPT Lookup'''</big></u>: {{#lst:Glossary\|GPT Lookup}}~~

	~~<u><big>'''Lookup'''</big></u>: {{#lst:Glossary\|Lookup}}~~

Dgreenwood: Dgreenwood moved page 2023:GPT Lookup (Lookup) to 2023:GPT Lookup (Lookup Specification) without leaving a redirect

2024-10-04T20:29:39Z

Dgreenwood moved page 2023:GPT Lookup (Lookup) to 2023:GPT Lookup (Lookup Specification) without leaving a redirect

← Older revision	Revision as of 15:29, 4 October 2024
(No difference)

Randallkinard: Randallkinard moved page GPT Lookup (Lookup) to 2023:GPT Lookup (Lookup)

2024-08-28T16:03:58Z

Randallkinard moved page GPT Lookup (Lookup) to 2023:GPT Lookup (Lookup)

← Older revision	Revision as of 11:03, 28 August 2024
(No difference)

Randallkinard at 13:46, 27 August 2024

2024-08-27T13:46:43Z

@@ Line 2: / Line 2: @@
 <blockquote>{{#lst:Glossary|GPT Lookup}}</blockquote>
 == About ==
@@ Line 192: / Line 177: @@
 [[Image:GPT Integration 048.png]]

Randallkinard at 14:07, 10 May 2024

2024-05-10T14:07:45Z

← Older revision		Revision as of 09:07, 10 May 2024
Line 2:		Line 2:

	<blockquote>{{#lst:Glossary\|GPT Lookup}}</blockquote>		<blockquote>{{#lst:Glossary\|GPT Lookup}}</blockquote>

			== Glossary ==
			<u><big>'''Data Field'''</big></u>: {{#lst:Glossary\|Data Field}}

			<u><big>'''Data Model'''</big></u>: {{#lst:Glossary\|Data Model}}

			<u><big>'''Execute'''</big></u>: {{#lst:Glossary\|Execute}}

			<u><big>'''GPT Complete'''</big></u>: {{#lst:Glossary\|GPT Complete}}

			<u><big>'''GPT Integration'''</big></u>: {{#lst:Glossary\|GPT Integration}}

			<u><big>'''GPT Lookup'''</big></u>: {{#lst:Glossary\|GPT Lookup}}

			<u><big>'''Lookup'''</big></u>: {{#lst:Glossary\|Lookup}}

	== About ==		== About ==

Randallkinard: Created page with "{{AutoVersion}}
{{#lst:Glossary|GPT Lookup}}
== About == === Lookup Properties === Following are brief descriptions of properties that are unique to GPT Lookup. ==== API Key ==== You must fill this property with a valid API key from OpenAI in order to leverage GPT integration with Grooper. See the '''Obtain an API Key''' section of the GPT Integration article for ins..."

2024-04-30T15:18:37Z

Created page with "{{AutoVersion}} <blockquote>{{#lst:Glossary|GPT Lookup}}</blockquote> == About == === Lookup Properties === Following are brief descriptions of properties that are unique to GPT Lookup. ==== API Key ==== You must fill this property with a valid API key from OpenAI in order to leverage GPT integration with Grooper. See the '''Obtain an API Key''' section of the GPT Integration article for ins..."

New page

{{AutoVersion}}

<blockquote>{{#lst:Glossary|GPT Lookup}}</blockquote>

== About ==
=== Lookup Properties ===
Following are brief descriptions of properties that are unique to GPT Lookup.

==== API Key ====
You must fill this property with a valid API key from OpenAI in order to leverage GPT integration with Grooper. See the '''[[GPT Integration (Concept)#Obtain an API Key|Obtain an API Key]]''' section of the [[GPT Integration (Concept)|GPT Integration]] article for instruction on how to get a key.

==== Model ====
The API Key you use will determine which GPT models are available to you. The different GPT models can affect the text generated based on their size, training data, capabilities, prompt engineering, and fine-tuning potential. GPT-3's larger size and training data, in particular, can potentially result in more sophisticated, diverse, and contextually appropriate text compared to GPT-2. However, the actual performance and quality of the generated text also depend on various other factors, such as prompt engineering, input provided, and specific use case requirements. GPT-4 is the latest version, as of this writing, and takes the GPT model even further.

==== Parameters ====
===== Temperature =====
In the context of text generation using language models like ChatGPT, the temperature parameter is a setting that controls the randomness or randomness of the generated text. It is used during the sampling process, where the model selects the next word or token to generate based on its predicted probabilities.

When generating text, the language model assigns probabilities to different words or tokens based on their likelihood of occurring next in the context of the input text. The temperature parameter is used to scale these probabilities before sampling from them. A higher temperature value (e.g., 1.0) makes the probabilities more uniform and increases randomness, resulting in more varied and diverse text. On the other hand, a lower temperature value (e.g., 0.2) makes the probabilities more concentrated and biased towards the most likely word, resulting in more deterministic and focused text.

For example, with a higher temperature setting, the model may generate sentences like:
: ''"The weather is hot and sunny. I love to go swimming or hiking."''

With a lower temperature setting, the model may generate sentences like:
: ''"The weather is hot. I love to go swimming."''

The choice of temperature parameter depends on the desired output. Higher values are useful when you want more creativity and diversity in the generated text, but it may lead to less coherent or nonsensical sentences. Lower values are useful when you want more deterministic and focused text, but it may result in repetitive or overly conservative output. It's a hyperparameter that can be tuned to achieve the desired balance between randomness and coherence in the generated text.

===== TopP =====
TopP, also known as "nucleus sampling" or "stochastic decoding with dynamic vocabulary," is a text generation technique that is used to improve the diversity and randomness of generated text. It is often used as an alternative to traditional approaches like random sampling or greedy decoding in language models, such as GPT-2 and GPT-3.

In TopP sampling, instead of sampling from the entire probability distribution of possible next words or tokens, the model narrows down the choices to a subset of the most likely options. The subset is determined dynamically based on a predefined probability threshold, denoted as "p". The model considers only the words or tokens whose cumulative probability mass (probability of occurrence) falls within the top "p" value. The remaining words or tokens with lower probabilities are pruned from the selection.

Mathematically, given a probability distribution over all possible words or tokens, TopP sampling works as follows:

# Compute the cumulative distribution function (CDF) of the probabilities for the given distribution.
# Sort the probabilities in descending order and calculate the cumulative sum of probabilities from highest to lowest.
# Stop when the cumulative sum exceeds the threshold "p". So 0.1 means only the tokens comprising the top 10% probability mass are considered.
# The remaining set of words or tokens whose probabilities fall within the threshold "p" is considered for sampling.
By using TopP sampling, the model can generate text that is more diverse, as it allows for the possibility of selecting less frequent or rarer words or tokens, and it introduces randomness in the selection process. It can prevent the model from becoming overly deterministic or repetitive in its generated output, leading to more creative and varied text generation results.

===== Presence Penalty =====
The "presence penalty" is a technique used in text generation to encourage the model to generate more concise and focused outputs by penalizing the repetition of the same words or tokens in the generated text. It is a regularization technique that aims to reduce redundancy and promote diversity in the generated output.

The presence penalty is typically implemented as an additional term in the loss function during the training process of a language model. This term penalizes the model for generating the same words or tokens multiple times within a short span of text. The presence penalty can be formulated in different ways, depending on the specific model architecture and objectives, but the general idea is to assign a higher loss or penalty when the model generates repetitive or redundant text.

The presence penalty encourages the model to generate text that is more concise, avoids repetitive patterns, and promotes the use of a wider vocabulary. It helps prevent the model from generating overly verbose or redundant text, which can be undesirable in certain text generation tasks, such as story generation or summarization.

The magnitude of the presence penalty can be tuned to control the level of repetition allowed in the generated text. A higher penalty value would result in stricter avoidance of repetition, while a lower penalty value would allow for more repetition. The presence penalty is one of the techniques that can be used in combination with other regularization methods, such as temperature scaling, top-k sampling, or fine-tuning, to improve the quality and diversity of generated text.

===== Frequency Penalty =====
Frequency-based regularization techniques in text generation can refer to methods that aim to control the distribution of word or token frequencies in the generated text. This can be achieved by adding penalties or constraints to the model during training, such as limiting the occurrence of certain words or tokens, promoting the use of less frequent words or tokens, or controlling the balance of word or token frequencies in the generated text.

==== Response Format ====
This specifies the format in which data will be exchanged with the web service. Can be one of the following values:
* '''Text''' - The response will be plain text. Record and value selectors should be specified using regular expressions.
* '''JSON''' - The response will be in JSON format. Record and value selectors should be specified using [https://www.ietf.org/archive/id/draft-goessner-dispatch-jsonpath-00.html JSONPath] syntax.
* '''XML''' - The request and response body will be in XML format. Record and value selectors should be specified using [https://en.wikipedia.org/wiki/XPath XPath] syntax.

The format selected here will be used both for sending POST data and interpreting responses. It is currently not possible to send an XML request then interpret the response as JSON, or vice-versa.

==== Record Selector ====
This is a JSONPath or XPath expression which selects records in the response.

The record selector is used to specify which JSON or XML entities represent records in the result set.

: '''JSON Notes'''
:: In a JSON response, the Record Selector may be used as follows:
::* If the selector matches an array, one record will be generated for each element of the array.
::* If the selector matches one or more objects, one record will be generated for each object.
::* Leave the property empty to select an array or object at the root of the JSON document.

: '''XML Notes'''
:: In an XML response, the Record Selector may be used as follows:
::* One record will be generated for each XML element matched by the selector.
::* Leave the property empty to select a singleton record at the root of the XML.

==== Timeout ====
The amount of time, in seconds, to wait for a response from the web service before raising a timeout error.

== How To ==
Following is a simple of example that will demonstrate how to use the ''GPT Lookup'' functionality. As with everything else regarding GPT Integration in Grooper 2023, this is fairly untested and needs more experimentation to see its full potential. If nothing else, this example is intended to give you a basic understanding of how to establish the lookup so you can try things out on your own.

# Start by deleting all other fields in the example '''Data Model''' other than "Lessor" and "Lessee".
#* This is meant to reduce the number of calls you will be making to OpenAI for GPT results as "Lessor" and "Lessee" are the only '''Data Fields''' that will be leveraged in the following lookup example.

[[Image:GPT Integration 034.png]]

# <li value=2> Right-click the '''Data Model'''.
# Add a '''Data Field'''.

[[Image:GPT Integration 035.png]]

# <li value=4> Name it "Letter of Thanks".
# Click the "Execute" button.

[[Image:GPT Integration 036.png]]

# <li value=6> With the newly created '''Data Field''' object selected, set the '''''Display Width''''' property to ''500''.
# Set the '''''Multi-line''''' property to ''Enabled''.
# Expand the sub-properties of the '''''Multi Line''''' property and set the '''''Display Lines''''' property to ''15''.
# Set the '''''Word Wrap''''' property to ''True''.

[[Image:GPT Integration 037.png]]

# <li value=10> Select the '''Data Model'''.
# Click the ellipsis button on the '''''Lookups''''' property.

[[Image:GPT Integration 038.png]]

# <li value=12> In the "Lookups" window, click the "Add new lookups specification" button.
# Select the "GPT Lookup" option.

[[Image:GPT Integration 039.png]]

# <li value=14> With the "GPT Lookup" added to the "List of Lookup Specification" and selected, paste in your API key to the '''''API Key''''' property.
# Click the ellipsis button for the '''''Prompt''''' property.

[[Image:GPT Integration 040.png]]

# <li value=16> In the "Prompt" editor, type the following string:
#* <code>Write a letter of thanks regarding the ease of purchase and clean state of the property from <span style="color:#00b400;">@Lessor</span> to <span style="color:#00b400;">@Lessee</span>.</code>
#* As you type this out (if you do instead of copy pasting) you will notice intellisense pop-up for when you use the <code style="color:#00b400;">@</code> symbol. Using the <code style="color:#00b400;">@</code> symbol allows you to leverage elements from your '''Data Model''' when creating your lookup.
# When you have completed writing your prompt, click the "OK" button.

[[Image:GPT Integration 041.png]]

# <li value=18> Click the ellipsis button for the '''''Value Selectors''''' property.

[[Image:GPT Integration 042.png]]

# <li value=19> In the "Value Selectors" window click the "Add new value selector" button.

[[Image:GPT Integration 043.png]]

# <li value=20> With "Value Selector" added to the "list of Value Selector" and selected, click the drop-down button for the '''''Target Field''''' property.
# Select the "Letter_of_Thanks" field.
#* Based on this configuration, the value generated by our prompt from our lookup will populate this field with the information generated by GPT.

[[Image:GPT Integration 044.png]]

# <li value=22> Back in the "Lookups" menu, scroll down in the property grid, and in the "Lookup Options" area click the drop-down button for the '''''Trigger Mode''''' property.
# Because <code style="color:#00b400;">@</code> symbols are being used in the prompt to leverage elements from the '''Data Model''' the ''Conditional'' setting should be selected.

[[Image:GPT Integration 045.png]]

# <li value=24> At the bottom of the property grid notice the '''''Lookup Fields''''' and '''''Target Fields''''' are populated because elements were targeted in the prompt, and a field was targeted with the '''''Value Selectors''''' property.
# Click "OK" to close this menu.

[[Image:GPT Integration 046.png]]

# <li value=26> With the lookup configured it's time to test. Click the "Tester" tab.
# Select "Folder (1)" from the "GPT Complete Examples" batch.
# Click the "Test the data element" button.
# Notice the "Lessee" value is successfully returned ...
# ... and that it is being leveraged as the salutation in the value created for the "Letter of Thanks" field.

[[Image:GPT Integration 047.png]]

# <li value=31> Also notice the "Lessor" value being returned ...
# ... and that it is being leveraged as the complementary close in the value created for the "Letter of Thanks" field.
# Feel free to take a look at the text created for the letter from the GPT AI.

[[Image:GPT Integration 048.png]]

2023:GPT Lookup (Lookup Specification) - Revision history

Dgreenwood at 21:43, 27 August 2025

Randallkinard at 19:39, 21 November 2024

Dgreenwood: Dgreenwood moved page 2023:GPT Lookup (Lookup) to 2023:GPT Lookup (Lookup Specification) without leaving a redirect

Randallkinard: Randallkinard moved page GPT Lookup (Lookup) to 2023:GPT Lookup (Lookup)

Randallkinard at 13:46, 27 August 2024

Randallkinard at 14:07, 10 May 2024