mirror of
https://github.com/microsoft/graphrag.git
synced 2025-12-27 15:10:00 +00:00
Deploying to gh-pages from @ microsoft/graphrag@3b1e70c06b 🚀
This commit is contained in:
natoverse
parent
46947763db
commit
22bb80fb50
@ -1455,7 +1455,7 @@
|
||||
<a id="__codelineno-0-6" name="__codelineno-0-6" href="#__codelineno-0-6"></a> api_key: ${GRAPHRAG_API_KEY}
|
||||
</code></pre></div>
|
||||
<h1 id="config-sections">Config Sections</h1>
|
||||
<h2 id="indexing">Indexing</h2>
|
||||
<h2 id="language-model-setup">Language Model Setup</h2>
|
||||
<h3 id="models">models</h3>
|
||||
<p>This is a dict of model configurations. The dict key is used to reference this configuration elsewhere when a model instance is desired. In this way, you can specify as many different models as you need, and reference them differentially in the workflow steps.</p>
|
||||
<p>For example:
|
||||
@ -1473,137 +1473,155 @@
|
||||
<h4 id="fields">Fields</h4>
|
||||
<ul>
|
||||
<li><code>api_key</code> <strong>str</strong> - The OpenAI API key to use.</li>
|
||||
<li><code>type</code> <strong>openai_chat|azure_openai_chat|openai_embedding|azure_openai_embedding</strong> - The type of LLM to use.</li>
|
||||
<li><code>auth_type</code> <strong>api_key|managed_identity</strong> - Indicate how you want to authenticate requests.</li>
|
||||
<li><code>type</code> <strong>openai_chat|azure_openai_chat|openai_embedding|azure_openai_embedding|mock_chat|mock_embeddings</strong> - The type of LLM to use.</li>
|
||||
<li><code>model</code> <strong>str</strong> - The model name.</li>
|
||||
<li><code>encoding_model</code> <strong>str</strong> - The text encoding model to use. Default is to use the encoding model aligned with the language model (i.e., it is retrieved from tiktoken if unset).</li>
|
||||
<li><code>max_tokens</code> <strong>int</strong> - The maximum number of output tokens.</li>
|
||||
<li><code>request_timeout</code> <strong>float</strong> - The per-request timeout.</li>
|
||||
<li><code>api_base</code> <strong>str</strong> - The API base url to use.</li>
|
||||
<li><code>api_version</code> <strong>str</strong> - The API version.</li>
|
||||
<li><code>deployment_name</code> <strong>str</strong> - The deployment name to use (Azure).</li>
|
||||
<li><code>organization</code> <strong>str</strong> - The client organization.</li>
|
||||
<li><code>proxy</code> <strong>str</strong> - The proxy URL to use.</li>
|
||||
<li><code>azure_auth_type</code> <strong>api_key|managed_identity</strong> - if using Azure, please indicate how you want to authenticate requests.</li>
|
||||
<li><code>audience</code> <strong>str</strong> - (Azure OpenAI only) The URI of the target Azure resource/service for which a managed identity token is requested. Used if <code>api_key</code> is not defined. Default=<code>https://cognitiveservices.azure.com/.default</code></li>
|
||||
<li><code>deployment_name</code> <strong>str</strong> - The deployment name to use (Azure).</li>
|
||||
<li><code>model_supports_json</code> <strong>bool</strong> - Whether the model supports JSON-mode output.</li>
|
||||
<li><code>request_timeout</code> <strong>float</strong> - The per-request timeout.</li>
|
||||
<li><code>tokens_per_minute</code> <strong>int</strong> - Set a leaky-bucket throttle on tokens-per-minute.</li>
|
||||
<li><code>requests_per_minute</code> <strong>int</strong> - Set a leaky-bucket throttle on requests-per-minute.</li>
|
||||
<li><code>retry_strategy</code> <strong>str</strong> - Retry strategy to use, "native" is the default and uses the strategy built into the OpenAI SDK. Other allowable values include "exponential_backoff", "random_wait", and "incremental_wait".</li>
|
||||
<li><code>max_retries</code> <strong>int</strong> - The maximum number of retries to use.</li>
|
||||
<li><code>max_retry_wait</code> <strong>float</strong> - The maximum backoff time.</li>
|
||||
<li><code>sleep_on_rate_limit_recommendation</code> <strong>bool</strong> - Whether to adhere to sleep recommendations (Azure).</li>
|
||||
<li><code>concurrent_requests</code> <strong>int</strong> The number of open requests to allow at once.</li>
|
||||
<li><code>async_mode</code> <strong>asyncio|threaded</strong> The async mode to use. Either <code>asyncio</code> or <code>threaded</code>.</li>
|
||||
<li><code>responses</code> <strong>list[str]</strong> - If this model type is mock, this is a list of response strings to return.</li>
|
||||
<li><code>max_tokens</code> <strong>int</strong> - The maximum number of output tokens.</li>
|
||||
<li><code>temperature</code> <strong>float</strong> - The temperature to use.</li>
|
||||
<li><code>top_p</code> <strong>float</strong> - The top-p value to use.</li>
|
||||
<li><code>n</code> <strong>int</strong> - The number of completions to generate.</li>
|
||||
<li><code>parallelization_stagger</code> <strong>float</strong> - The threading stagger value.</li>
|
||||
<li><code>parallelization_num_threads</code> <strong>int</strong> - The maximum number of work threads.</li>
|
||||
<li><code>async_mode</code> <strong>asyncio|threaded</strong> The async mode to use. Either <code>asyncio</code> or `threaded.</li>
|
||||
<li><code>frequency_penalty</code> <strong>float</strong> - Frequency penalty for token generation.</li>
|
||||
<li><code>presence_penalty</code> <strong>float</strong> - Frequency penalty for token generation.</li>
|
||||
</ul>
|
||||
<h3 id="embed_text">embed_text</h3>
|
||||
<p>By default, the GraphRAG indexer will only export embeddings required for our query methods. However, the model has embeddings defined for all plaintext fields, and these can be customized by setting the <code>target</code> and <code>names</code> fields.</p>
|
||||
<p>Supported embeddings names are:
|
||||
- <code>text_unit.text</code>
|
||||
- <code>document.text</code>
|
||||
- <code>entity.title</code>
|
||||
- <code>entity.description</code>
|
||||
- <code>relationship.description</code>
|
||||
- <code>community.title</code>
|
||||
- <code>community.summary</code>
|
||||
- <code>community.full_content</code></p>
|
||||
<h2 id="input-files-and-chunking">Input Files and Chunking</h2>
|
||||
<h3 id="input">input</h3>
|
||||
<p>Our pipeline can ingest .csv, .txt, or .json data from an input folder. See the <a href="../../index/inputs/">inputs page</a> for more details and examples.</p>
|
||||
<h4 id="fields_1">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|blob</strong> - The input type to use. Default=<code>file</code></li>
|
||||
<li><code>file_type</code> <strong>text|csv|json</strong> - The type of input data to load. Default is <code>text</code></li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to read input from, relative to the root.</li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob only) The Azure Storage connection string.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - The storage account blob URL to use.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob only) The Azure Storage container name.</li>
|
||||
<li><code>encoding</code> <strong>str</strong> - The encoding of the input file. Default is <code>utf-8</code></li>
|
||||
<li><code>file_pattern</code> <strong>str</strong> - A regex to match input files. Default is <code>.*\.csv$</code>, <code>.*\.txt$</code>, or <code>.*\.json$</code> depending on the specified <code>file_type</code>, but you can customize it if needed.</li>
|
||||
<li><code>file_filter</code> <strong>dict</strong> - Key/value pairs to filter. Default is None.</li>
|
||||
<li><code>text_column</code> <strong>str</strong> - (CSV/JSON only) The text column name. If unset we expect a column named <code>text</code>.</li>
|
||||
<li><code>title_column</code> <strong>str</strong> - (CSV/JSON only) The title column name, filename will be used if unset.</li>
|
||||
<li><code>metadata</code> <strong>list[str]</strong> - (CSV/JSON only) The additional document attributes fields to keep.</li>
|
||||
</ul>
|
||||
<h3 id="chunks">chunks</h3>
|
||||
<p>These settings configure how we parse documents into text chunks. This is necessary because very large documents may not fit into a single context window, and graph extraction accuracy can be modulated. Also note the <code>metadata</code> setting in the input document config, which will replicate document metadata into each chunk.</p>
|
||||
<h4 id="fields_2">Fields</h4>
|
||||
<ul>
|
||||
<li><code>size</code> <strong>int</strong> - The max chunk size in tokens.</li>
|
||||
<li><code>overlap</code> <strong>int</strong> - The chunk overlap in tokens.</li>
|
||||
<li><code>group_by_columns</code> <strong>list[str]</strong> - Group documents by these fields before chunking.</li>
|
||||
<li><code>strategy</code> <strong>str</strong>[tokens|sentences] - How to chunk the text. </li>
|
||||
<li><code>encoding_model</code> <strong>str</strong> - The text encoding model to use for splitting on token boundaries.</li>
|
||||
<li><code>prepend_metadata</code> <strong>bool</strong> - Determines if metadata values should be added at the beginning of each chunk. Default=<code>False</code>.</li>
|
||||
<li><code>chunk_size_includes_metadata</code> <strong>bool</strong> - Specifies whether the chunk size calculation should include metadata tokens. Default=<code>False</code>.</li>
|
||||
</ul>
|
||||
<h2 id="outputs-and-storage">Outputs and Storage</h2>
|
||||
<h3 id="output">output</h3>
|
||||
<p>This section controls the storage mechanism used by the pipeline used for exporting output tables.</p>
|
||||
<h4 id="fields_3">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|memory|blob|cosmosdb</strong> - The storage type to use. Default=<code>file</code></li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to write output artifacts to, relative to the root.</li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob/cosmosdb only) The Azure Storage connection string.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob/cosmosdb only) The Azure Storage container name.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - (blob only) The storage account blob URL to use.</li>
|
||||
<li><code>cosmosdb_account_blob_url</code> <strong>str</strong> - (cosmosdb only) The CosmosDB account blob URL to use.</li>
|
||||
</ul>
|
||||
<h3 id="update_index_output">update_index_output</h3>
|
||||
<p>The section defines a secondary storage location for running incremental indexing, to preserve your original outputs.</p>
|
||||
<h4 id="fields_4">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|memory|blob|cosmosdb</strong> - The storage type to use. Default=<code>file</code></li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to write output artifacts to, relative to the root.</li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob/cosmosdb only) The Azure Storage connection string.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob/cosmosdb only) The Azure Storage container name.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - (blob only) The storage account blob URL to use.</li>
|
||||
<li><code>cosmosdb_account_blob_url</code> <strong>str</strong> - (cosmosdb only) The CosmosDB account blob URL to use.</li>
|
||||
</ul>
|
||||
<h3 id="cache">cache</h3>
|
||||
<p>This section controls the cache mechanism used by the pipeline. This is used to cache LLM invocation results for faster performance when re-running the indexing process.</p>
|
||||
<h4 id="fields_5">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|memory|blob|cosmosdb</strong> - The storage type to use. Default=<code>file</code></li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to write output artifacts to, relative to the root.</li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob/cosmosdb only) The Azure Storage connection string.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob/cosmosdb only) The Azure Storage container name.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - (blob only) The storage account blob URL to use.</li>
|
||||
<li><code>cosmosdb_account_blob_url</code> <strong>str</strong> - (cosmosdb only) The CosmosDB account blob URL to use.</li>
|
||||
</ul>
|
||||
<h3 id="reporting">reporting</h3>
|
||||
<p>This section controls the reporting mechanism used by the pipeline, for common events and error messages. The default is to write reports to a file in the output directory. However, you can also choose to write reports to the console or to an Azure Blob Storage container.</p>
|
||||
<h4 id="fields_6">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|console|blob</strong> - The reporting type to use. Default=<code>file</code></li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to write reports to, relative to the root.</li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob only) The Azure Storage connection string.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob only) The Azure Storage container name.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - The storage account blob URL to use.</li>
|
||||
</ul>
|
||||
<h3 id="vector_store">vector_store</h3>
|
||||
<p>Where to put all vectors for the system. Configured for lancedb by default. This is a dict, with the key used to identify individual store parameters (e.g., for text embedding).</p>
|
||||
<h4 id="fields_7">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>lancedb|azure_ai_search|cosmosdb</strong> - Type of vector store. Default=<code>lancedb</code></li>
|
||||
<li><code>db_uri</code> <strong>str</strong> (only for lancedb) - The database uri. Default=<code>storage.base_dir/lancedb</code></li>
|
||||
<li><code>url</code> <strong>str</strong> (only for AI Search) - AI Search endpoint</li>
|
||||
<li><code>api_key</code> <strong>str</strong> (optional - only for AI Search) - The AI Search api key to use.</li>
|
||||
<li><code>audience</code> <strong>str</strong> (only for AI Search) - Audience for managed identity token if managed identity authentication is used.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - The name of a vector container. This stores all indexes (tables) for a given dataset ingest. Default=<code>default</code></li>
|
||||
<li><code>database_name</code> <strong>str</strong> - (cosmosdb only) Name of the database.</li>
|
||||
<li><code>overwrite</code> <strong>bool</strong> (only used at index creation time) - Overwrite collection if it exist. Default=<code>True</code></li>
|
||||
</ul>
|
||||
<h2 id="workflow-configurations">Workflow Configurations</h2>
|
||||
<p>These settings control each individual workflow as they execute.</p>
|
||||
<h3 id="workflows">workflows</h3>
|
||||
<p><strong>list[str]</strong> - This is a list of workflow names to run, in order. GraphRAG has built-in pipelines to configure this, but you can run exactly and only what you want by specifying the list here. Useful if you have done part of the processing yourself.</p>
|
||||
<h3 id="embed_text">embed_text</h3>
|
||||
<p>By default, the GraphRAG indexer will only export embeddings required for our query methods. However, the model has embeddings defined for all plaintext fields, and these can be customized by setting the <code>target</code> and <code>names</code> fields.</p>
|
||||
<p>Supported embeddings names are:</p>
|
||||
<ul>
|
||||
<li><code>text_unit.text</code></li>
|
||||
<li><code>document.text</code></li>
|
||||
<li><code>entity.title</code></li>
|
||||
<li><code>entity.description</code></li>
|
||||
<li><code>relationship.description</code></li>
|
||||
<li><code>community.title</code></li>
|
||||
<li><code>community.summary</code></li>
|
||||
<li><code>community.full_content</code></li>
|
||||
</ul>
|
||||
<h4 id="fields_8">Fields</h4>
|
||||
<ul>
|
||||
<li><code>model_id</code> <strong>str</strong> - Name of the model definition to use for text embedding.</li>
|
||||
<li><code>vector_store_id</code> <strong>str</strong> - Name of vector store definition to write to.</li>
|
||||
<li><code>batch_size</code> <strong>int</strong> - The maximum batch size to use.</li>
|
||||
<li><code>batch_max_tokens</code> <strong>int</strong> - The maximum batch # of tokens.</li>
|
||||
<li><code>target</code> <strong>required|all|selected|none</strong> - Determines which set of embeddings to export.</li>
|
||||
<li><code>names</code> <strong>list[str]</strong> - If target=selected, this should be an explicit list of the embeddings names we support.</li>
|
||||
</ul>
|
||||
<h3 id="vector_store">vector_store</h3>
|
||||
<p>Where to put all vectors for the system. Configured for lancedb by default.</p>
|
||||
<h4 id="fields_2">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>str</strong> - <code>lancedb</code> or <code>azure_ai_search</code>. Default=<code>lancedb</code></li>
|
||||
<li><code>db_uri</code> <strong>str</strong> (only for lancedb) - The database uri. Default=<code>storage.base_dir/lancedb</code></li>
|
||||
<li><code>url</code> <strong>str</strong> (only for AI Search) - AI Search endpoint</li>
|
||||
<li><code>api_key</code> <strong>str</strong> (optional - only for AI Search) - The AI Search api key to use.</li>
|
||||
<li><code>audience</code> <strong>str</strong> (only for AI Search) - Audience for managed identity token if managed identity authentication is used.</li>
|
||||
<li><code>overwrite</code> <strong>bool</strong> (only used at index creation time) - Overwrite collection if it exist. Default=<code>True</code></li>
|
||||
<li><code>container_name</code> <strong>str</strong> - The name of a vector container. This stores all indexes (tables) for a given dataset ingest. Default=<code>default</code></li>
|
||||
</ul>
|
||||
<h3 id="input">input</h3>
|
||||
<p>Our pipeline can ingest .csv or .txt data from an input folder. These files can be nested within subfolders. In general, CSV-based data provides the most customizability. Each CSV should at least contain a <code>text</code> field. You can use the <code>metadata</code> list to specify additional columns from the CSV to include as headers in each text chunk, allowing you to repeat document content within each chunk for better LLM inclusion.</p>
|
||||
<h4 id="fields_3">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|blob</strong> - The input type to use. Default=<code>file</code></li>
|
||||
<li><code>file_type</code> <strong>text|csv</strong> - The type of input data to load. Either <code>text</code> or <code>csv</code>. Default is <code>text</code></li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to read input from, relative to the root.</li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob only) The Azure Storage connection string.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - The storage account blob URL to use.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob only) The Azure Storage container name.</li>
|
||||
<li><code>file_encoding</code> <strong>str</strong> - The encoding of the input file. Default is <code>utf-8</code></li>
|
||||
<li><code>file_pattern</code> <strong>str</strong> - A regex to match input files. Default is <code>.*\.csv$</code> if in csv mode and <code>.*\.txt$</code> if in text mode.</li>
|
||||
<li><code>file_filter</code> <strong>dict</strong> - Key/value pairs to filter. Default is None.</li>
|
||||
<li><code>text_column</code> <strong>str</strong> - (CSV Mode Only) The text column name.</li>
|
||||
<li><code>metadata</code> <strong>list[str]</strong> - (CSV Mode Only) The additional document attributes to include.</li>
|
||||
</ul>
|
||||
<h3 id="chunks">chunks</h3>
|
||||
<p>These settings configure how we parse documents into text chunks. This is necessary because very large documents may not fit into a single context window, and graph extraction accuracy can be modulated. Also note the <code>metadata</code> setting in the input document config, which will replicate document metadata into each chunk.</p>
|
||||
<h4 id="fields_4">Fields</h4>
|
||||
<ul>
|
||||
<li><code>size</code> <strong>int</strong> - The max chunk size in tokens.</li>
|
||||
<li><code>overlap</code> <strong>int</strong> - The chunk overlap in tokens.</li>
|
||||
<li><code>group_by_columns</code> <strong>list[str]</strong> - group documents by fields before chunking.</li>
|
||||
<li><code>encoding_model</code> <strong>str</strong> - The text encoding model to use for splitting on token boundaries.</li>
|
||||
<li><code>prepend_metadata</code> <strong>bool</strong> - Determines if metadata values should be added at the beginning of each chunk. Default=<code>False</code>.</li>
|
||||
<li><code>chunk_size_includes_metadata</code> <strong>bool</strong> - Specifies whether the chunk size calculation should include metadata tokens. Default=<code>False</code>.</li>
|
||||
</ul>
|
||||
<h3 id="cache">cache</h3>
|
||||
<p>This section controls the cache mechanism used by the pipeline. This is used to cache LLM invocation results.</p>
|
||||
<h4 id="fields_5">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|memory|none|blob</strong> - The cache type to use. Default=<code>file</code></li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob only) The Azure Storage connection string.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob only) The Azure Storage container name.</li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to write cache to, relative to the root.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - The storage account blob URL to use.</li>
|
||||
</ul>
|
||||
<h3 id="output">output</h3>
|
||||
<p>This section controls the storage mechanism used by the pipeline used for exporting output tables.</p>
|
||||
<h4 id="fields_6">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|memory|blob</strong> - The storage type to use. Default=<code>file</code></li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob only) The Azure Storage connection string.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob only) The Azure Storage container name.</li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to write output artifacts to, relative to the root.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - The storage account blob URL to use.</li>
|
||||
</ul>
|
||||
<h3 id="update_index_storage">update_index_storage</h3>
|
||||
<p>The section defines a secondary storage location for running incremental indexing, to preserve your original outputs.</p>
|
||||
<h4 id="fields_7">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|memory|blob</strong> - The storage type to use. Default=<code>file</code></li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob only) The Azure Storage connection string.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob only) The Azure Storage container name.</li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to write output artifacts to, relative to the root.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - The storage account blob URL to use.</li>
|
||||
</ul>
|
||||
<h3 id="reporting">reporting</h3>
|
||||
<p>This section controls the reporting mechanism used by the pipeline, for common events and error messages. The default is to write reports to a file in the output directory. However, you can also choose to write reports to the console or to an Azure Blob Storage container.</p>
|
||||
<h4 id="fields_8">Fields</h4>
|
||||
<ul>
|
||||
<li><code>type</code> <strong>file|console|blob</strong> - The reporting type to use. Default=<code>file</code></li>
|
||||
<li><code>connection_string</code> <strong>str</strong> - (blob only) The Azure Storage connection string.</li>
|
||||
<li><code>container_name</code> <strong>str</strong> - (blob only) The Azure Storage container name.</li>
|
||||
<li><code>base_dir</code> <strong>str</strong> - The base directory to write reports to, relative to the root.</li>
|
||||
<li><code>storage_account_blob_url</code> <strong>str</strong> - The storage account blob URL to use.</li>
|
||||
</ul>
|
||||
<h3 id="extract_graph">extract_graph</h3>
|
||||
<p>Tune the language model-based graph extraction process.</p>
|
||||
<h4 id="fields_9">Fields</h4>
|
||||
<ul>
|
||||
<li><code>model_id</code> <strong>str</strong> - Name of the model definition to use for API calls.</li>
|
||||
<li><code>prompt</code> <strong>str</strong> - The prompt file to use.</li>
|
||||
<li><code>entity_types</code> <strong>list[str]</strong> - The entity types to identify.</li>
|
||||
<li><code>max_gleanings</code> <strong>int</strong> - The maximum number of gleaning cycles to use.</li>
|
||||
<li><code>encoding_model</code> <strong>str</strong> - The text encoding model to use. Default is to use the encoding model aligned with the language model (i.e., it is retrieved from tiktoken if unset). This is only used for gleanings during the logit_bias check.</li>
|
||||
</ul>
|
||||
<h3 id="summarize_descriptions">summarize_descriptions</h3>
|
||||
<h4 id="fields_10">Fields</h4>
|
||||
@ -1629,26 +1647,9 @@
|
||||
<li>noun_phrase_tags <strong>list[str]</strong> - List of noun phrase tags to ignore.</li>
|
||||
<li>noun_phrase_grammars <strong>dict[str, str]</strong> - Noun phrase grammars for the model (cfg-only).</li>
|
||||
</ul>
|
||||
<h3 id="extract_claims">extract_claims</h3>
|
||||
<h4 id="fields_12">Fields</h4>
|
||||
<ul>
|
||||
<li><code>enabled</code> <strong>bool</strong> - Whether to enable claim extraction. Off by default, because claim prompts really need user tuning.</li>
|
||||
<li><code>model_id</code> <strong>str</strong> - Name of the model definition to use for API calls.</li>
|
||||
<li><code>prompt</code> <strong>str</strong> - The prompt file to use.</li>
|
||||
<li><code>description</code> <strong>str</strong> - Describes the types of claims we want to extract.</li>
|
||||
<li><code>max_gleanings</code> <strong>int</strong> - The maximum number of gleaning cycles to use.</li>
|
||||
</ul>
|
||||
<h3 id="community_reports">community_reports</h3>
|
||||
<h4 id="fields_13">Fields</h4>
|
||||
<ul>
|
||||
<li><code>model_id</code> <strong>str</strong> - Name of the model definition to use for API calls.</li>
|
||||
<li><code>prompt</code> <strong>str</strong> - The prompt file to use.</li>
|
||||
<li><code>max_length</code> <strong>int</strong> - The maximum number of output tokens per report.</li>
|
||||
<li><code>max_input_length</code> <strong>int</strong> - The maximum number of input tokens to use when generating reports.</li>
|
||||
</ul>
|
||||
<h3 id="prune_graph">prune_graph</h3>
|
||||
<p>Parameters for manual graph pruning. This can be used to optimize the modularity of your graph clusters, by removing overly-connected or rare nodes.</p>
|
||||
<h4 id="fields_14">Fields</h4>
|
||||
<h4 id="fields_12">Fields</h4>
|
||||
<ul>
|
||||
<li>min_node_freq <strong>int</strong> - The minimum node frequency to allow.</li>
|
||||
<li>max_node_freq_std <strong>float | None</strong> - The maximum standard deviation of node frequency to allow.</li>
|
||||
@ -1660,17 +1661,36 @@
|
||||
</ul>
|
||||
<h3 id="cluster_graph">cluster_graph</h3>
|
||||
<p>These are the settings used for Leiden hierarchical clustering of the graph to create communities.</p>
|
||||
<h4 id="fields_15">Fields</h4>
|
||||
<h4 id="fields_13">Fields</h4>
|
||||
<ul>
|
||||
<li><code>max_cluster_size</code> <strong>int</strong> - The maximum cluster size to export.</li>
|
||||
<li><code>use_lcc</code> <strong>bool</strong> - Whether to only use the largest connected component.</li>
|
||||
<li><code>seed</code> <strong>int</strong> - A randomization seed to provide if consistent run-to-run results are desired. We do provide a default in order to guarantee clustering stability.</li>
|
||||
</ul>
|
||||
<h3 id="extract_claims">extract_claims</h3>
|
||||
<h4 id="fields_14">Fields</h4>
|
||||
<ul>
|
||||
<li><code>enabled</code> <strong>bool</strong> - Whether to enable claim extraction. Off by default, because claim prompts really need user tuning.</li>
|
||||
<li><code>model_id</code> <strong>str</strong> - Name of the model definition to use for API calls.</li>
|
||||
<li><code>prompt</code> <strong>str</strong> - The prompt file to use.</li>
|
||||
<li><code>description</code> <strong>str</strong> - Describes the types of claims we want to extract.</li>
|
||||
<li><code>max_gleanings</code> <strong>int</strong> - The maximum number of gleaning cycles to use.</li>
|
||||
<li><code>encoding_model</code> <strong>str</strong> - The text encoding model to use. Default is to use the encoding model aligned with the language model (i.e., it is retrieved from tiktoken if unset). This is only used for gleanings during the logit_bias check.</li>
|
||||
</ul>
|
||||
<h3 id="community_reports">community_reports</h3>
|
||||
<h4 id="fields_15">Fields</h4>
|
||||
<ul>
|
||||
<li><code>model_id</code> <strong>str</strong> - Name of the model definition to use for API calls.</li>
|
||||
<li><code>prompt</code> <strong>str</strong> - The prompt file to use.</li>
|
||||
<li><code>max_length</code> <strong>int</strong> - The maximum number of output tokens per report.</li>
|
||||
<li><code>max_input_length</code> <strong>int</strong> - The maximum number of input tokens to use when generating reports.</li>
|
||||
</ul>
|
||||
<h3 id="embed_graph">embed_graph</h3>
|
||||
<p>We use node2vec to embed the graph. This is primarily used for visualization, so it is not turned on by default. However, if you do prefer to embed the graph for secondary analysis, you can turn this on and we will persist the embeddings to your configured vector store.</p>
|
||||
<p>We use node2vec to embed the graph. This is primarily used for visualization, so it is not turned on by default.</p>
|
||||
<h4 id="fields_16">Fields</h4>
|
||||
<ul>
|
||||
<li><code>enabled</code> <strong>bool</strong> - Whether to enable graph embeddings.</li>
|
||||
<li><code>dimensions</code> <strong>int</strong> - Number of vector dimensions to produce.</li>
|
||||
<li><code>num_walks</code> <strong>int</strong> - The node2vec number of walks.</li>
|
||||
<li><code>walk_length</code> <strong>int</strong> - The node2vec walk length.</li>
|
||||
<li><code>window_size</code> <strong>int</strong> - The node2vec window size.</li>
|
||||
@ -1778,8 +1798,6 @@
|
||||
<li><code>max_tokens</code> <strong>int</strong> - The maximum tokens.</li>
|
||||
<li><code>llm_max_tokens</code> <strong>int</strong> - The LLM maximum tokens.</li>
|
||||
</ul>
|
||||
<h3 id="workflows">workflows</h3>
|
||||
<p><strong>list[str]</strong> - This is a list of workflow names to run, in order. GraphRAG has built-in pipelines to configure this, but you can run exactly and only what you want by specifying the list here. Useful if you have done part of the processing yourself.</p>
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2432,7 +2432,7 @@ search = DRIFTSearch(
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
100%|██████████| 1/1 [00:12<00:00, 12.57s/it]</pre>
|
||||
<pre>
100%|██████████| 1/1 [00:13<00:00, 13.62s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
@ -2456,13 +2456,19 @@ search = DRIFTSearch(
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
33%|███▎ | 1/3 [00:14<00:29, 14.67s/it]</pre>
|
||||
<pre>
33%|███▎ | 1/3 [00:14<00:29, 14.73s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
67%|██████▋ | 2/3 [00:18<00:08, 8.46s/it]</pre>
|
||||
<pre>
67%|██████▋ | 2/3 [00:16<00:06, 6.85s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
100%|██████████| 3/3 [00:21<00:00, 6.40s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
@ -2486,19 +2492,19 @@ search = DRIFTSearch(
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
33%|███▎ | 1/3 [00:10<00:21, 10.91s/it]</pre>
|
||||
<pre>
33%|███▎ | 1/3 [00:10<00:20, 10.17s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
67%|██████▋ | 2/3 [00:11<00:04, 4.96s/it]</pre>
|
||||
<pre>
67%|██████▋ | 2/3 [00:10<00:04, 4.43s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
100%|██████████| 3/3 [00:14<00:00, 3.79s/it]</pre>
|
||||
<pre>
100%|██████████| 3/3 [00:11<00:00, 2.81s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
@ -2522,19 +2528,19 @@ search = DRIFTSearch(
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
33%|███▎ | 1/3 [00:08<00:16, 8.49s/it]</pre>
|
||||
<pre>
33%|███▎ | 1/3 [00:09<00:18, 9.43s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
67%|██████▋ | 2/3 [00:09<00:03, 4.00s/it]</pre>
|
||||
<pre>
67%|██████▋ | 2/3 [00:12<00:05, 5.40s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="application/vnd.jupyter.stderr" tabindex="0">
|
||||
<pre>
100%|██████████| 3/3 [00:09<00:00, 2.23s/it]</pre>
|
||||
<pre>
100%|██████████| 3/3 [00:13<00:00, 3.59s/it]</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
@ -2585,7 +2591,7 @@ search = DRIFTSearch(
|
||||
<div class="jp-OutputArea-child jp-OutputArea-executeResult">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt">Out[7]:</div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output jp-OutputArea-executeResult" data-mime-type="text/plain" tabindex="0">
|
||||
<pre>"Agent Alex Mercer is a pivotal figure within the Paranormal Military Squad, playing a crucial role in Operation: Dulce, which involves exploring and investigating the Dulce base rumored to house advanced alien technology. Mercer is recognized for his leadership qualities and serves as a mentor to fellow agent Sam Rivera, emphasizing intuition and trust in navigating the mission's uncertainties [Data: Reports (0, 1)].\n\nMercer's leadership style is collaborative and supportive, fostering open communication and valuing team members' insights and instincts. This approach helps build camaraderie and mutual respect within the team [Data: Reports (1)]. He works closely with other key team members, such as Dr. Jordan Hayes, who provides expertise in alien technology, and Taylor Cruz, whose authoritative leadership style contrasts with Mercer's more intuitive approach [Data: Reports (0, 1)].\n\nOverall, Mercer's ability to foster trust and intuition among his team members, coupled with his collaborative efforts, highlights his significance in the mission to explore and understand the Dulce base and its alien technology [Data: Reports (0)]."</pre>
|
||||
<pre>"Agent Alex Mercer is a pivotal member of the Paranormal Military Squad, playing a crucial role in Operation: Dulce. He is known for his leadership and mentorship abilities, which are essential to the success of the mission. Mercer's role involves guiding and supporting fellow team members, particularly Sam Rivera, and fostering trust and intuition within the team [Data: Reports (1); Sources (3, 0)].\n\nMercer is also noted for his determination and ability to maintain focus under pressure, as well as his reflective nature, which allows him to consider the broader implications of their mission beyond immediate objectives [Data: Sources (3)]. His interactions with other team members, such as Taylor Cruz and Jordan Hayes, highlight his ability to balance protocol with adaptability, encouraging open communication and collaboration [Data: Reports (1); Sources (0, 3)].\n\nOverall, Mercer's skills in leadership, mentorship, focus, and reflective thinking make him an invaluable asset to the Paranormal Military Squad, particularly in the complex and high-stakes environment of Operation: Dulce [Data: Reports (1); Sources (3)]."</pre>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@ -2624,18 +2630,40 @@ search = DRIFTSearch(
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="text/plain" tabindex="0">
|
||||
<pre>{"How does Alex Mercer's leadership style differ from Taylor Cruz's?": {'reports': id title \
|
||||
<pre>{'What specific skills does Agent Mercer bring to the Paranormal Military Squad?': {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
1 2 differently than praise from others. This was...
|
||||
2 3 contrast to the rigid silence enveloping the ...
|
||||
0 3 contrast to the rigid silence enveloping the ...
|
||||
1 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 2 differently than praise from others. This was...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, 'What are the potential implications of the discoveries at the Dulce base?': {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 2 differently than praise from others. This was...
|
||||
1 3 contrast to the rigid silence enveloping the ...
|
||||
2 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
3 4 a mask of duty.\n\nIn the midst of the descen...
|
||||
4 1 , the hollow echo of the bay a stark reminder ...}, "How do Agent Mercer's relationships with other team members influence the mission?": {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 2 differently than praise from others. This was...
|
||||
1 3 contrast to the rigid silence enveloping the ...
|
||||
2 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
3 1 , the hollow echo of the bay a stark reminder ...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, 'What is the significance of the Dulce base in Operation: Dulce?': {'reports': id title \
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, 'What specific technologies are being explored at the Dulce base?': {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
@ -2646,18 +2674,7 @@ Index: [], 'sources': id text
|
||||
1 3 contrast to the rigid silence enveloping the ...
|
||||
2 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
3 4 a mask of duty.\n\nIn the midst of the descen...
|
||||
4 1 , the hollow echo of the bay a stark reminder ...}, "How does Sam Rivera benefit from Alex Mercer's mentorship?": {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 3 contrast to the rigid silence enveloping the ...
|
||||
1 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 2 differently than praise from others. This was...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, 'What are the key challenges faced by the Paranormal Military Squad in Operation: Dulce?': {'reports': id title \
|
||||
4 1 , the hollow echo of the bay a stark reminder ...}, 'What role does agent Mercer play in the exploration of the Dulce base?': {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
@ -2667,63 +2684,52 @@ Index: [], 'sources': id text
|
||||
0 2 differently than praise from others. This was...
|
||||
1 3 contrast to the rigid silence enveloping the ...
|
||||
2 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
3 4 a mask of duty.\n\nIn the midst of the descen...
|
||||
4 1 , the hollow echo of the bay a stark reminder ...}, 'What challenges does Sam Rivera face during Operation: Dulce?': {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
1 2 differently than praise from others. This was...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 3 contrast to the rigid silence enveloping the ...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, 'What specific role does Alex Mercer play in overcoming these challenges?': {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 3 contrast to the rigid silence enveloping the ...
|
||||
1 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 2 differently than praise from others. This was...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, "What specific instances demonstrate Alex Mercer's mentorship approach?": {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 3 contrast to the rigid silence enveloping the ...
|
||||
1 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 2 differently than praise from others. This was...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, "In what ways do Alex Mercer's and Taylor Cruz's leadership styles complement each other?": {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
1 2 differently than praise from others. This was...
|
||||
2 3 contrast to the rigid silence enveloping the ...
|
||||
3 1 , the hollow echo of the bay a stark reminder ...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, 'What specific protocols does Taylor Cruz emphasize during Operation: Dulce?': {'reports': id title \
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, "How does Mercer's mentorship impact Sam Rivera's performance during the mission?": {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 2 differently than praise from others. This was...
|
||||
1 3 contrast to the rigid silence enveloping the ...
|
||||
2 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
3 4 a mask of duty.\n\nIn the midst of the descen...
|
||||
4 1 , the hollow echo of the bay a stark reminder ...}}
|
||||
0 3 contrast to the rigid silence enveloping the ...
|
||||
1 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 2 differently than praise from others. This was...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, "In what ways do Mercer's interactions with Taylor Cruz affect the team's decision-making process?": {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 3 contrast to the rigid silence enveloping the ...
|
||||
1 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 2 differently than praise from others. This was...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, "What role does intuition play in Mercer's decision-making process?": {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 3 contrast to the rigid silence enveloping the ...
|
||||
1 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 2 differently than praise from others. This was...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}, "In what ways does Mercer's mentorship of Sam Rivera influence the team's operations?": {'reports': id title \
|
||||
0 1 Paranormal Military Squad and Operation: Dulce
|
||||
|
||||
content
|
||||
0 # Paranormal Military Squad and Operation: Dul... , 'entities': Empty DataFrame
|
||||
Columns: [in_context]
|
||||
Index: [], 'sources': id text
|
||||
0 3 contrast to the rigid silence enveloping the ...
|
||||
1 0 # Operation: Dulce\n\n## Chapter 1\n\nThe thru...
|
||||
2 1 , the hollow echo of the bay a stark reminder ...
|
||||
3 2 differently than praise from others. This was...
|
||||
4 4 a mask of duty.\n\nIn the midst of the descen...}}
|
||||
</pre>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -2541,15 +2541,19 @@ print(result.response)</div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="text/plain" tabindex="0">
|
||||
<pre>### Overview of Operation: Dulce
|
||||
|
||||
Operation: Dulce is a significant mission undertaken by the Paranormal Military Squad, an elite group tasked with investigating alien technology and its implications for humanity. The operation focuses on the exploration and uncovering of secrets within the Dulce base, which is central to the mission's objectives [Data: Reports (0)].
|
||||
Operation: Dulce is a significant mission undertaken by the Paranormal Military Squad, focusing on the investigation of alien technology and its implications for humanity. This operation is centered around the exploration and uncovering of secrets within the Dulce base, which is known for its association with advanced alien technology. The mission's complexity and importance are underscored by the strategic objectives tied to understanding and potentially harnessing this technology [Data: Reports (0)].
|
||||
|
||||
### Key Elements and Objectives
|
||||
### Key Participants
|
||||
|
||||
The Dulce base is associated with advanced alien technology, making it a crucial element in the mission. The exploration of this base is vital for the success of Operation: Dulce, as it involves navigating its depths to uncover hidden technologies and secrets that may have profound implications for humanity [Data: Reports (1)].
|
||||
The operation is executed by the Paranormal Military Squad, which includes key agents such as Alex Mercer, Taylor Cruz, Jordan Hayes, and Sam Rivera. The involvement of these agents is critical to the mission's success, as their expertise and dedication are essential in navigating the challenges posed by the Dulce base [Data: Reports (1)].
|
||||
|
||||
### Team and Motivation
|
||||
### Mission Objectives
|
||||
|
||||
The mission is executed by key agents of the Paranormal Military Squad, including Alex Mercer, Taylor Cruz, Jordan Hayes, and Sam Rivera. Each of these agents plays a significant role in the operation, driven by a strong sense of duty to navigate the complexities of the Dulce base and achieve the mission's objectives [Data: Reports (1, 0)].
|
||||
The primary objective of Operation: Dulce is to explore the depths of the Dulce base and investigate the advanced alien technology housed within. This technology is crucial to the mission's goals and the overall success of the operation. The agents are tasked with uncovering the secrets of the base, which may have significant implications for humanity [Data: Reports (1)].
|
||||
|
||||
### Motivation and Challenges
|
||||
|
||||
A strong sense of duty drives the individuals involved in Operation: Dulce. This motivation is a key factor in their willingness to undertake the mission and face the complexities associated with the Dulce base. The operation requires navigating a range of challenges, emphasizing the importance of the agents' commitment and resolve [Data: Reports (0)].
|
||||
</pre>
|
||||
</div>
|
||||
</div>
|
||||
@ -2709,9 +2713,9 @@ print(
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="text/plain" tabindex="0">
|
||||
<pre>Build context (gpt-4o)
|
||||
LLM calls: 2. Prompt tokens: 1761. Output tokens: 208.
|
||||
LLM calls: 2. Prompt tokens: 1761. Output tokens: 209.
|
||||
Map-reduce (gpt-4o)
|
||||
LLM calls: 2. Prompt tokens: 3378. Output tokens: 493.
|
||||
LLM calls: 2. Prompt tokens: 3378. Output tokens: 591.
|
||||
</pre>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -3366,21 +3366,21 @@ print(result.response)</div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="text/plain" tabindex="0">
|
||||
<pre>### Overview of Agent Alex Mercer
|
||||
|
||||
Agent Alex Mercer is a prominent member of the Paranormal Military Squad, an elite group tasked with executing Operation: Dulce. He plays a crucial role in the mission, providing guidance and emphasizing the importance of intuition and trust among his team members. Mercer's leadership and mentorship are particularly significant, as he serves as a mentor to Sam Rivera, offering valuable support and leadership [Data: Reports (1); Entities (0); Relationships (2, 15)].
|
||||
|
||||
### Role in Operation: Dulce
|
||||
|
||||
In Operation: Dulce, Alex Mercer is one of the agents exploring the Dulce base, a mysterious and secretive location associated with advanced alien technology. His involvement in the mission is critical, as he is responsible for leading the team into the Dulce base and navigating its complexities. Mercer's leadership is characterized by a balance between compliance with protocols and a natural inclination to question and explore all details, which sometimes leads to internal conflict [Data: Reports (1); Entities (0, 8); Relationships (23, 4); Claims (3, 5)].
|
||||
|
||||
### Relationships and Interactions
|
||||
|
||||
Agent Mercer maintains professional relationships with other key members of the Paranormal Military Squad, including Taylor Cruz, Jordan Hayes, and Sam Rivera. His relationship with Taylor Cruz is primarily professional, with Mercer acknowledging Cruz's authority while also experiencing a competitive undercurrent due to Cruz's authoritative nature. With Jordan Hayes, Mercer shares a mutual respect and understanding, particularly admiring each other's expertise and analytical abilities. His mentorship of Sam Rivera highlights his role as a guiding figure within the team [Data: Reports (1); Entities (0, 1, 2, 3); Relationships (0, 1, 2, 15)].
|
||||
Agent Alex Mercer is a pivotal member of the Paranormal Military Squad, an elite group tasked with executing Operation: Dulce. His role is crucial to the mission's success, as he is one of the agents exploring the Dulce base, a mysterious and secretive location associated with advanced alien technology [Data: Reports (1); Entities (0, 8); Relationships (23, 4)].
|
||||
|
||||
### Leadership and Mentorship
|
||||
|
||||
Alex Mercer's leadership style is marked by his emphasis on intuition and trust, which he believes are essential for the success of their mission. His mentorship of Sam Rivera is a testament to his commitment to nurturing the skills and potential of his team members. This mentorship is not only about imparting knowledge but also about fostering a sense of confidence and readiness in facing the unknown challenges of Operation: Dulce [Data: Reports (1); Entities (0, 3); Relationships (2, 15)].
|
||||
Alex Mercer is recognized for his leadership qualities and serves as a mentor to Sam Rivera, another key member of the squad. He provides guidance and emphasizes the importance of intuition and trust, which are essential traits for navigating the complexities of Operation: Dulce. His mentorship relationship with Sam Rivera highlights his supportive nature and his ability to foster talent within the team [Data: Reports (1); Entities (0, 3); Relationships (2, 15)].
|
||||
|
||||
In summary, Agent Alex Mercer is a key figure in the Paranormal Military Squad, whose leadership and mentorship are vital to the success of Operation: Dulce. His ability to balance protocol with intuition, along with his strong professional relationships, underscores his importance in the mission and his role as a mentor to his colleagues.
|
||||
### Professional Relationships
|
||||
|
||||
Mercer maintains professional relationships with other team members, including Taylor Cruz and Jordan Hayes. His interactions with Taylor Cruz are marked by a competitive undercurrent, as Cruz's authoritative nature often challenges Mercer's compliance. Despite this, Mercer acknowledges Cruz's authority and follows their lead during the mission [Data: Reports (1); Entities (0, 1, 2); Relationships (0, 1)].
|
||||
|
||||
### Internal Conflict and Role in Operation: Dulce
|
||||
|
||||
Agent Mercer experiences internal conflict between adhering to protocols and his natural inclination to question and explore all details. This conflict is evident in his interactions with Taylor Cruz and his own reflections on the mission. Despite these challenges, Mercer is depicted as a determined individual who is leading a mission into the Dulce base, indicating his significant role in mission leadership and decision-making [Data: Claims (3, 5); Reports (1); Entities (0)].
|
||||
|
||||
In summary, Agent Alex Mercer is a key figure in the Paranormal Military Squad, known for his leadership, mentorship, and professional relationships. His role in Operation: Dulce is critical, as he navigates the complexities of the mission while managing internal conflicts and fostering teamwork among his colleagues.
|
||||
</pre>
|
||||
</div>
|
||||
</div>
|
||||
@ -3424,27 +3424,27 @@ print(result.response)</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="text/plain" tabindex="0">
|
||||
<pre>### Overview of Dr. Jordan Hayes
|
||||
<pre>## Overview of Dr. Jordan Hayes
|
||||
|
||||
Dr. Jordan Hayes is a prominent scientist and a key member of the Paranormal Military Squad, known for their expertise in physics and composed demeanor. They play a significant role in Operation: Dulce, particularly in working with alien technology, which is a central element of the mission [Data: Entities (2); Reports (1)].
|
||||
|
||||
### Role in Operation: Dulce
|
||||
## Role in Operation: Dulce
|
||||
|
||||
Dr. Hayes is deeply involved in the exploration of the Dulce base, where they contribute their analytical skills to the mission. Their work primarily focuses on understanding and analyzing alien technology, which is crucial for the success of Operation: Dulce. This role highlights their importance in the mission, as they provide valuable insights and expertise in dealing with the complexities of alien technology [Data: Reports (1); Entities (2, 13); Relationships (26, 48, 51)].
|
||||
Dr. Hayes is deeply involved in the exploration of the Dulce base, where they contribute their analytical skills to the mission. Their work primarily focuses on understanding and manipulating alien technology, which is crucial for the success of Operation: Dulce. Hayes is recognized for their analytical mind and reflective nature, often contemplating the complexities of their missions [Data: Reports (1); Entities (2, 13)].
|
||||
|
||||
### Professional Relationships
|
||||
## Professional Relationships
|
||||
|
||||
Dr. Hayes maintains professional relationships with other key members of the Paranormal Military Squad, including Taylor Cruz, Sam Rivera, and Alex Mercer. Their interactions with these team members emphasize the importance of adaptability and analytical thinking in the mission. Dr. Hayes is known for their skepticism towards strict adherence to protocols, advocating for a more flexible approach to the unknown variables encountered during the mission [Data: Reports (1); Relationships (1, 5, 9, 25)].
|
||||
Dr. Hayes maintains professional relationships with other key members of the Paranormal Military Squad, including Taylor Cruz, Sam Rivera, and Alex Mercer. Their interactions with Taylor Cruz are marked by differing views on protocol and adaptability, highlighting a complex relationship characterized by moments of mutual respect. With Sam Rivera, Hayes shares a common belief in the importance of adaptability, which is essential for the mission's success [Data: Reports (1); Relationships (5, 9, 25)].
|
||||
|
||||
### Analytical and Skeptical Nature
|
||||
## Analytical and Skeptical Nature
|
||||
|
||||
Dr. Hayes is portrayed as a skeptical and analytical member of the team, often contemplating the layers of data and the complexities of their missions. This skepticism is particularly evident in their interactions with Taylor Cruz, where they emphasize the need for adaptability over rigid protocols. Their analytical insights are crucial in identifying hidden elements within the Dulce base, such as a suspicious panel that seemed out of place [Data: Claims (2, 6, 10); Sources (0, 2)].
|
||||
Dr. Hayes is portrayed as skeptical of strict adherence to protocols, emphasizing the need for adaptability and acknowledging the unknown variables that exceed the known. This skepticism is evident in their interactions and comments during mission briefings. They provide analytical insights and express concerns about the mission, indicating a role in analytical assessment [Data: Claims (2, 6); Sources (0)].
|
||||
|
||||
### Contribution to the Team
|
||||
## Contributions and Discoveries
|
||||
|
||||
Dr. Hayes' contribution to the Paranormal Military Squad is significant, as they bring a reflective and analytical perspective to the mission. Their ability to navigate the complexities of alien technology and their composed demeanor make them a valuable asset to the team. Their role in Operation: Dulce underscores the importance of scientific expertise and adaptability in dealing with the unknown challenges posed by the mission [Data: Reports (1); Entities (2); Relationships (10, 18, 21)].
|
||||
During the mission, Dr. Hayes identified a suspicious panel that seemed out of place, indicating a hidden element within the Dulce base. This discovery underscores their role in uncovering critical aspects of the mission and highlights their importance in the team's efforts to navigate the complexities of the Dulce base [Data: Claims (10); Sources (2)].
|
||||
|
||||
In summary, Dr. Jordan Hayes is a critical member of the Paranormal Military Squad, whose expertise in physics and alien technology plays a vital role in the success of Operation: Dulce. Their analytical nature and professional relationships with other team members highlight the importance of adaptability and scientific insight in navigating the complexities of the mission.
|
||||
In summary, Dr. Jordan Hayes is a vital member of the Paranormal Military Squad, contributing their scientific expertise and analytical skills to Operation: Dulce. Their role in working with alien technology and their professional relationships with other team members are crucial to the mission's success.
|
||||
</pre>
|
||||
</div>
|
||||
</div>
|
||||
@ -3968,7 +3968,7 @@ print(candidate_questions.response)</div>
|
||||
<div class="jp-OutputArea-child">
|
||||
<div class="jp-OutputPrompt jp-OutputArea-prompt"></div>
|
||||
<div class="jp-RenderedText jp-OutputArea-output" data-mime-type="text/plain" tabindex="0">
|
||||
<pre>['- What is the role of Agent Alex Mercer in Operation: Dulce?', "- How does Agent Taylor Cruz's leadership style impact the team's mission at Dulce base?", '- What expertise does Dr. Jordan Hayes bring to the exploration of the Dulce base?', '- How does Sam Rivera contribute to the mission at Dulce base with their cybersecurity skills?', '- What are the dynamics and relationships among the Paranormal Military Squad members during Operation: Dulce?']
|
||||
<pre>['- What is the role of Agent Alex Mercer in Operation: Dulce?', "- How does Agent Taylor Cruz's leadership style impact the Paranormal Military Squad's mission?", '- What expertise does Dr. Jordan Hayes bring to the exploration of the Dulce base?', '- How does Sam Rivera contribute to the success of Operation: Dulce?', '- What are the dynamics and relationships among the members of the Paranormal Military Squad during their mission at the Dulce base?']
|
||||
</pre>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
File diff suppressed because one or more lines are too long
Loading…
x
Reference in New Issue
Block a user