You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build/mapping-creator/index.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ tags:
9
9
10
10
## Configuration Info
11
11
12
-
A specific configuration is require to activate this feature.
13
-
Furthermore, for best experience an LLM provider configuration is also needed.
12
+
A specific configuration is required to activate this feature.
13
+
Furthermore, for the best experience, an LLM provider configuration is also needed.
14
14
See the link in the info box for details.
15
15
16
16
!!! info "Configuration"
@@ -19,7 +19,7 @@ See the link in the info box for details.
19
19
20
20
## Usage
21
21
22
-
The Mapping Creator is a feature of BUILD transformation tasks (_BUILD_> _Project_> (_Workflow_>) _Transformation_> _Mapping Creator_).
22
+
The Mapping Creator is a feature of BUILD transformation tasks (_BUILD_> _Project_> (_Workflow_>) _Transformation_> _Mapping Creator_).
23
23
24
24
!!! question "Help"
25
25
@@ -28,7 +28,7 @@ The Mapping Creator is a feature of BUILD transformation tasks (_BUILD_> _Proje
28
28
Access help and a feature tour via the help menu :eccenca-item-question:.
29
29
30
30
Use the Mapping Creator to connect your data to semantic models.
31
-
Using visual tools, drag-and-drop, and suggestions, you are able to create mappings between your source data and knowledge graph classes as well as their properties.
31
+
Using visual tools, drag-and-drop, and suggestions, you can create mappings between your source data and knowledge graph classes as well as their properties.
To complete a mapping properties need to be added to complete your desired target schema (i.e. the graph fragment that your transformation shall yield).
64
+
To complete a mapping, properties need to be added to complete your desired target schema (i.e. the graph fragment that your transformation shall yield).
65
65
66
66
There are two options to add properties:
67
67
@@ -75,7 +75,7 @@ There are two options to add properties:
75
75
In the _add target class_ dialog you may select different kind of properties:
76
76
77
77
- class properties - properties defined in the domain of the selected class or its super-classes
78
-
- default properties - typical well knows like `rdfs:label` or `rdfs:comment`
78
+
- default properties - typical well-known properties like `rdfs:label` or `rdfs:comment`
79
79
- generic properties - properties defined with no explicit domain (or in domain of `owl:Thing`)
80
80
81
81
The property preview helps to confirm your choice.
@@ -84,7 +84,7 @@ The property preview helps to confirm your choice.
84
84
85
85
{ class="bordered" width="80%" }
86
86
87
-
The _add property from vocabularies_ dialog allows to search and select a property and to configure it in the desired way:
87
+
The _add property from vocabularies_ dialog allows you to search and select a property and to configure it in the desired way:
88
88
89
89
- redefine the role of a property, to use a DatatypeProperty in the role of an ObjectProperty, or vice versa
90
90
- define the _direction_ an ObjectProperty should be used in
@@ -126,7 +126,7 @@ You can accept (:octicons-thumbsup-16:) or reject (:octicons-thumbsdown-16:) eac
Copy file name to clipboardExpand all lines: docs/explore-and-author/companion/index.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,20 +11,22 @@ The Companion view enables you to interact with your data, graphs, vocabularies,
11
11
12
12
## Configuration Info
13
13
14
-
A specific configuration is require to activate this feature.
15
-
Our deployment templates (helm charts and docker-compose configurations) provide testes configuration profiles for different LLM providers.
14
+
A specific configuration is required to activate this feature.
15
+
Our deployment templates (helm charts and docker-compose configurations) provide tested configuration profiles for different LLM providers.
16
16
See the link in the info box for details.
17
17
18
18
!!! info "Configuration"
19
19
20
20
See [`spring.ai.*` configuration properties in _Configuration of Servlet Container_](../../deploy-and-configure/configuration/explore/dataplatform/application-full.md#configuration-of-servlet-container) to learn how to enable and configure this feature.
21
21
Explore uses _Spring AI_ to connect and configure LLM provider, as such the [Spring AI Chat Model API Configuration Reference](https://docs.spring.io/spring-ai/reference/api/chatmodel.html) applies.
22
22
23
+
For optimal results, we recommend using Anthropic or OpenAI frontier-level models configured through the native Spring AI provider setup.
24
+
23
25
## Usage
24
26
25
27
{ class="bordered" width="40%" }
26
28
27
-
You can open the _Chat with Companion_ from any explore module via the :eccenca-application-ai-suggestion: Companion button the top right of the application header, next to the :eccenca-application-useraccount: user menu.
29
+
You can open the _Chat with Companion_ from any explore module via the :eccenca-application-ai-suggestion: Companion button in the top right of the application header, next to the :eccenca-application-useraccount: user menu.
@@ -33,13 +35,13 @@ In the companion sidebar, use:
33
35
- :eccenca-toggler-maximize: to increase the size of the sidebar
34
36
- :eccenca-toggler-minimize: to decrease the size of the sidebar
35
37
- :eccenca-item-add-artefact: to start a new conversation
36
-
- the dropdown menu to select or search for a conversation
38
+
-:octicons-triangle-down-24: the dropdown menu to select or search for a conversation
37
39
- :eccenca-item-upload: to add documents as context to the chat (supported formats include `pdf`, `txt` and `md`)
38
40
- :eccenca-item-wrench: to configure the tools that the LLM can use to answer.
39
-
- :eccenca-item-wrench: to use your microphone to dictate your questions
41
+
- :eccenca-item-microphone: to use your microphone to dictate your questions
40
42
- :material-send-variant-outline: to submit your question
41
43
42
-
To maximise the relevance and accuracy of the generated answer, your question is automatically enriched based on the context of the current view (e.g. the query text, the graph and the resource IRI).
44
+
To maximize the relevance and accuracy of the generated answer, your question is automatically enriched based on the context of the current view (e.g. the query text, the graph and the resource IRI).
43
45
44
46
### Tool selection
45
47
@@ -59,7 +61,7 @@ If your use case or question requires you to limit the available tools (e.g. if
59
61
60
62
`query_execute_saved`
61
63
: Executes a saved SPARQL query on this corporate memory instance.
62
-
The query is identified by it's IRI.
64
+
The query is identified by its IRI.
63
65
64
66
- Query related:
65
67
@@ -86,17 +88,17 @@ If your use case or question requires you to limit the available tools (e.g. if
86
88
87
89
`vocabularies_property_list`
88
90
: All Properties defined in this knowledge graph by installed vocabularies.
89
-
While all properties are returned, they can easy be grouped by either their explicit association with an ontology in the isDefinedBy (`rdfs:isDefinedBy`) field, or by the sourceGraph field, which contains the names of the graphs from which the type statements were loaded from.
91
+
While all properties are returned, they can easily be grouped by either their explicit association with an ontology in the isDefinedBy (`rdfs:isDefinedBy`) field, or by the sourceGraph field, which contains the names of the graphs from which the type statements were loaded.
90
92
91
93
`vocabularies_class_list`
92
94
: All Classes defined in this knowledge graph by installed vocabularies.
93
-
While all classes are returned, they can easy be grouped by either their explicit association with an ontology in the isDefinedBy (`rdfs:isDefinedBy`) field, or by the sourceGraph field, which contains the names of the graphs from which the type statements were loaded from.
95
+
While all classes are returned, they can easily be grouped by either their explicit association with an ontology in the isDefinedBy (`rdfs:isDefinedBy`) field, or by the sourceGraph field, which contains the names of the graphs from which the type statements were loaded.
94
96
95
97
- Resource related
96
98
97
99
`resource_search`
98
100
: Performs a lucene syntax full text search of labels and descriptions for 'searchTerm' and retrieve list of best matches.
99
-
The context graph will restrict the search to it includes, or search the full graph. Pattern allows to define a `SPARQL WHERE` clause snippet, which defaults to `{GRAPH ?contextGraph {?resource ?p ?o}}`.
101
+
The context graph will restrict the search to its includes, or search the full graph. Pattern allows to define a `SPARQL WHERE` clause snippet, which defaults to `{GRAPH ?contextGraph {?resource ?p ?o}}`.
100
102
Search will always be on the `?resource`, so adjust the pattern, if needed.
Graph Insights allows you to explore your knowledge graph through grouped nodes and aggregated relations to keep the view readable.
14
+
Expansions are data-guided to avoid dead ends, while on-demand details give you context without clutter.
15
+
Interactive filters help you shape the exploration, building query paths with class, attribute, and relation filters along the way.
16
+
Each exploration can be converted to SPARQL, effectively serving as a no-code query builder. This also provides table-like views for users less familiar with graphs.
17
+
18
+
## Configuration Info
19
+
20
+
A specific configuration is required to activate this feature.
21
+
22
+
!!! info "Configuration"
23
+
24
+
See [Graph Insights Configuration](../../../deploy-and-configure/configuration/graphinsights/index.md) to learn how to enable and configure this feature.
12
25
26
+
<!--
13
27
## Usage
14
28
15
29
...
30
+
-->
16
31
17
32
## Management
18
33
19
34
In order to manage Graph Insights snapshots, you can use the
0 commit comments