Skip to content

Commit e1bbd4e

Browse files
committed
Nicer lists
1 parent f54cef3 commit e1bbd4e

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

docs/source/user_guide_kg_builder.rst

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -15,17 +15,17 @@ unstructured data.
1515

1616

1717
******************
18-
Pipeline structure
18+
Pipeline Structure
1919
******************
2020

2121
A Knowledge Graph (KG) construction pipeline requires a few components:
2222

23-
- Document **parser**: extract text from files (PDFs, ...)
24-
- Document **chunker**: split the text into smaller pieces of text, manageable by the LLM context window (token limit).
25-
- Chunk **embedder** (optional): compute and store the chunk embeddings
23+
- **Document parser**: extract text from files (PDFs, ...).
24+
- **Document chunker**: split the text into smaller pieces of text, manageable by the LLM context window (token limit).
25+
- **Chunk embedder** (optional): compute the chunk embeddings.
2626
- **Schema builder**: provide a schema to ground the LLM extracted entities and relations and obtain an easily navigable KG.
2727
- **Entity and relation extractor**: extract relevant entities and relations from the text.
28-
- **Knowledge Graph writer**: write the identified entities and relations to a Neo4j database.
28+
- **Knowledge Graph writer**: save the identified entities and relations.
2929

3030
.. image:: images/kg_builder_pipeline.png
3131
:alt: KG Builder pipeline
@@ -171,9 +171,9 @@ Schema Builder
171171
The schema is used to try and ground the LLM to a list of possible entities and relations of interest.
172172
So far, schema must be manually created by specifying:
173173

174-
- The entities the LLM should look for in the text, including their properties (name and type)
175-
- The relations of interest between these entities, including the relation properties (name and type)
176-
- A list of possible triplets to define the start (source) and end (target) types for each relation
174+
- **Entities** the LLM should look for in the text, including their properties (name and type).
175+
- **Relations** of interest between these entities, including the relation properties (name and type).
176+
- **Triplets** to define the start (source) and end (target) entity types for each relation.
177177

178178
Here is a code block illustrating these concepts:
179179

@@ -317,9 +317,9 @@ The default prompt uses the :ref:`erextractiontemplate`. It is possible to provi
317317
318318
The following variables can be used in the prompt:
319319

320-
- `text` (str): the text to be analyzed
321-
- `schema` (str): the graph schema to be used
322-
- `examples` (str): examples for few-shot learning
320+
- `text` (str): the text to be analyzed.
321+
- `schema` (str): the graph schema to be used.
322+
- `examples` (str): examples for few-shot learning.
323323

324324

325325
Subclassing the EntityRelationExtractor

0 commit comments

Comments
 (0)