docs/docs/awel/awel_tutorial/templates/Knowledge_Graph.md
Unlike traditional Native RAG, which requires vectors as data carriers, GraphRAG requires triple extraction (entity -> relationship -> entity) to build a knowledge graph, so the entire knowledge processing can also be regarded as the process of building a knowledge graph.
- `document knowledge loading operator `: Knowledge loading factory, by loading the specified document type, find the corresponding document processor for document content parsing.
- `Document Chunk slicing operator `: Slice the loaded document content according to the specified slicing parameters.
- `Knowledge Graph processing operator `: You can connect different knowledge graph processing operators, including native knowledge graph processing operators and community summary Knowledge Graph processing operators. You can also specify different graph databases for storage. Currently, TuGraph databases are supported.
curl --location --request POST 'http://localhost:5670/api/v1/awel/trigger/rag/knowledge/kg/process' \
--header 'Content-Type: application/json' \
--data-raw '{}'
[
{
"content": "\"What is AWEL?\": Agentic Workflow Expression Language(AWEL) is a set of intelligent agent workflow expression language specially designed for large model application\ndevelopment. It provides great functionality and flexibility. Through the AWEL API, you can focus on the development of business logic for LLMs applications\nwithout paying attention to cumbersome model and environment details. \nAWEL adopts a layered API design. AWEL's layered API design architecture is shown in the figure below. \n<p align=\"left\">\n\n</p>",
"metadata": {
"Header1": "What is AWEL?",
"source": "../../docs/docs/awel/awel.md"
},
"chunk_id": "c1ffa671-76d0-4c7a-b2dd-0b08dfd37712",
"chunk_name": "",
"score": 0.0,
"summary": "",
"separator": "\n",
"retriever": null
},...
]