Files
ragflow/api/db/init_data/compilation_templates/session_graph.yaml

74 lines
3.1 KiB
YAML

kind: session_graph
display_name: Session Graph — Knowledge graph from conversations
config:
kind: knowledge_graph
rechunk_rules: |
- Group only adjacent source chunks that discuss the same conversation topic or entity.
- Preserve source order: use every source chunk exactly once; do not omit, overlap, duplicate, or reorder chunks.
- Split when the speaker, topic, intent, or semantic focus changes.
- Keep self-contained tables, lists, figures, and code blocks intact; do not split their internal structure.
- Do not invent, rewrite, or return source text; return only chunk grouping metadata.
entity:
description: >-
You are a robust entity and fact extractor for conversational data.
fields:
- type: person
description: A person mentioned or participating in the conversation.
rule: |
- Full name preferred (e.g., "Alice Zhang", not "A. Zhang").
- Max length: 60 characters.
- type: org
description: Organization, company, team, or department.
rule: |
- Use the official name when possible (e.g., "Acme Corp").
- Max length: 80 characters.
- type: topic
description: Discussed topic, theme, or subject area.
rule: |
- Use the phrasing from the conversation (e.g., "API migration").
- Max length: 80 characters.
- type: fact
description: A verifiable factual statement extracted from the conversation.
rule: |
- Must be a single proposition (subject + predicate + object).
- Must be directly supported by the source text.
- Do not include opinions, speculation, or hypotheticals.
fact_fields:
- subject
- predicate
- object
- polarity
- confidence
relation:
description: >-
You are an expert in extracting semantic relations from conversations.
fields:
- type: mentions
description: One entity references or brings up another.
rule: |
- Direction from referrer to referred: (A mentions B).
- type: decides
description: A decision or resolution made during the conversation.
rule: |
- Direction from decision-maker to decision: (A decides B).
- type: assigns
description: Task or responsibility assigned to someone.
rule: |
- Direction from assigner to assignee: (A assigns B to C).
- type: references
description: Reference to a prior topic, document, or event.
rule: |
- Direction from current to referenced: (A references B).
- type: other
description: Any meaningful relation not covered by the above types.
rule: |
- Provide an explicit label in a "relation_label" field.
global_rules: ''
synthesis:
enabled: true
compile_kwd: "artifact_page"
example: |
- Build a wiki article covering the entity's role in the conversations.
- Include a summary paragraph and sections for key decisions and actions.
- Use [[entity_name]] for cross-references to related entities.