Zǻi%ddlmZddlZddlmZmZddlmZmZGddZ Gdde Z Gd d e Z Gd d e Z Gd de Z y)) annotationsN)AnyOptional)PromptMissingInputErrorPromptMissingPlaceholderErrorcteZdZUdZdZded<dZded<eZded< d d d Z dd Z dd Z y)PromptTemplateaThis class is used to generate a parameterized prompt. It is defined from a string (the template) using the Python format syntax (parameters between curly braces `{}`) and a list of required inputs. Before sending the instructions to an LLM, call the `format` method that will replace parameters with the provided values. If any of the expected inputs is missing, a `PromptMissingInputError` is raised. strDEFAULT_SYSTEM_INSTRUCTIONSDEFAULT_TEMPLATEz list[str]EXPECTED_INPUTSNc|xs |j|_|xs |j|_|xs |j|_|jD]"}d|d|jvst d|y)N{}z"`template` is missing placeholder )r templaterexpected_inputsr system_instructionsr)selfrrres _/opt/lhia/marcimex/agent/venv/lib/python3.12/site-packages/neo4j_graphrag/generation/prompts.py__init__zPromptTemplate.__init__'s !9D$9$9 .F$2F2F  C4#C#C  %% AA3bz.38< c |jD]}||vstd|d|jjdi|S)NzMissing input '')rrrformat)rkwargsrs r_formatzPromptTemplate._format9sP%% FA-s!.DEE F$t}}##-f--rc|}|jt|j|Dcic]\}}|| c}}|jdi|Scc}}w)a1This method is used to replace parameters with the provided values. Parameters must be provided: - as kwargs - as args if using the same order as in the expected inputs Example: .. code-block:: python prompt_template = PromptTemplate( template='''Explain the following concept to {target_audience}: Concept: {concept} Answer: ''', expected_inputs=['target_audience', 'concept'] ) prompt = prompt_template.format('12 yo children', concept='graph database') print(prompt) # Result: # '''Explain the following concept to 12 yo children: # Concept: graph database # Answer: # ''' r)updateziprr)rargsrdatakvs rrzPromptTemplate.format?sO6 c$*>*>&EFdaQTFGt||#d##Gs A )NNN)r Optional[str]rzOptional[list[str]]rr'returnNone)rrr(r )r#rrrr(r ) __name__ __module__ __qualname____doc__r __annotations__r listrrrrrrrr r sk(*)c!%OY'#'/3-1 -+   $. $rr c0eZdZdZdZgdZdfd ZxZS) RagTemplatez4Answer the user question using the provided context.zJContext: {context} Examples: {examples} Question: {query_text} Answer: )context query_textexamplesc(t||||S)N)r3r2r4superr)rr3r2r4 __class__s rrzRagTemplate.formatnsw~Wx~XXr)r3r r2r r4r r(r )r*r+r,r r rr __classcell__r8s@rr1r1_s$"X hO  KKK K KKrrHc:eZdZdZdgZ d dfd ZxZS)SchemaExtractionTemplatea You are a top-tier algorithm designed for extracting a labeled property graph schema in structured formats. Generate a generalized graph schema based on the input text. Identify key node types, their relationship types, and property types. IMPORTANT RULES: 1. Return only abstract schema information, not concrete instances. 2. Use singular PascalCase labels for node types (e.g., Person, Company, Product). 3. Use UPPER_SNAKE_CASE labels for relationship types (e.g., WORKS_FOR, MANAGES). 4. Include property definitions only when the type can be confidently inferred, otherwise omit them. 5. When defining patterns, ensure that every node label and relationship label mentioned exists in your lists of node types and relationship types. 6. Do not create node types that aren't clearly mentioned in the text. 7. Keep your schema minimal and focused on clearly identifiable patterns in the text. 8. UNIQUENESS CONSTRAINTS: 8.1 UNIQUENESS is optional; each node_type may or may not have exactly one uniqueness constraint. 8.2 Only use properties that seem to not have too many missing values in the sample. 8.3 Constraints reference node_types by label and specify which property is unique. 8.4 If a property appears in a uniqueness constraint it MUST also appear in the corresponding node_type as a property. 9. REQUIRED PROPERTIES: 9.1 Mark a property as "required": true if every instance of that node/relationship type MUST have this property (non-nullable). 9.2 Mark a property as "required": false if the property is optional and may be absent on some instances. 9.3 Properties that are identifiers, names, or essential characteristics are typically required. 9.4 Properties that are supplementary information (phone numbers, descriptions, metadata) are typically optional. 9.5 When uncertain, default to "required": false. 9.6 If a property has a UNIQUENESS constraint, it MUST be marked as "required": true. Accepted property types are: BOOLEAN, DATE, DURATION, FLOAT, INTEGER, LIST, LOCAL_DATETIME, LOCAL_TIME, POINT, STRING, ZONED_DATETIME, ZONED_TIME. Return a valid JSON object that follows this precise structure: {{ "node_types": [ {{ "label": "Person", "properties": [ {{ "name": "name", "type": "STRING", "required": true }}, {{ "name": "email", "type": "STRING", "required": false }} ] }} ... ], "relationship_types": [ {{ "label": "WORKS_FOR" }} ... ], "patterns": [ {{"source": "Person", "relationship": "WORKS_FOR", "target": "Company"}}, ... ], "constraints": [ {{ "type": "UNIQUENESS", "node_type": "Person", "property_name": "name" }} ... ] }} Examples: {examples} Input text: {text} rIc&t|||S)N)rIr4r6)rrIr4r8s rrzSchemaExtractionTemplate.formats w~4(~;;r)r r )rIr r4r r(r rFr:s@rrLrLsDLZhO<<< <rQsZ#  B$B$JY.Y&- .- `(K>(KVU<~U