Repository and Graph Structure of Data Stored in Graph Modeling

21/11/2025

Graph Modeling supports configuration of an external graph database, which can be useful in the following cases:

Corpus ManagementCorpus Management - Overview
Exporting RDF Project DataExport RDF Project Data
Ontology Management
Sorting extraction results

The data created by Graph Modeling is spread across different repositories where each repository can be seen as one graph database.

Note

As of version 10.2, PoolParty has been rebranded to Graph Modeling. Despite our diligent efforts to maintain updated screenshots, some images from previous versions may appear in this section. We appreciate your patience during this transition.

Graph Modeling 10.0 and subsequent versions utilize an externalized GraphDB instance for all project and system repositories. This architectural change allows for independent scaling, high-availability setups, and decoupled maintenance of the GraphDB component. Refer to the GraphDB documentation for more information on your externalized GraphDB instance.

To view the GraphDB repositories storing your Graph Modeling data:

Open your web browser and navigate to the URL of your external GraphDB instance, typically: http(s)://your-server.com/graphdb/. Login with your credentials to access GraphDB.
Note
Your GraphDB instance may not be automatically accessible via the standard path http(s)://your-server.com/graphdb/ on all server configurations. If you require access to the GraphDB Workbench to utilize the SPARQL shell, please request it explicitly from your Graphwise representative. Credentials will be provided to you upon request.
Go to the Setup tab (1) on the left navigation bar
Within the Setup tab, click the Repositories sub-tab (2)
Tip
Individual project repositories are identifiable by their project titles (3) located next to the project UUID. If the title is not visible, try resizing the window or reducing the browser zoom level.

	Repository	Content description
System Repositories	PPT System	Metadata of all projects on a Graph Modeling Thesaurus server.
		Metadata of all corpora for all projects on a Graph Modeling Thesaurus server.
Project Repositories	Project repositories	Each repository contains project specific data only.
Project Repositories	Corpus repositories	Corpus data and the annotations from Corpus Management.Corpus Management - Overview
User Repository		Information on users and user groups.
Custom Schemes Repository		Metadata of all custom schemes and ontologies on a Graph Modeling Thesaurus server.
GraphSearch Repository		Metadata of all corpora for all projects on a Graph Modeling Thesaurus server.

The project repositories contain several named graphs. Default graphs are created when either the project or its first custom scheme is created. All optional graphs are only created if the respective data is available.

	Data	Graph name	Note
Default Graphs (Projects)	VoID	`<<baseUrl>/<projectId>/metadata/void>`	This graph contains metadata of the project e.g. number of concepts, creation date etc.
	ADMS	`<<baseUrl>/<projectId>/metadata/adms>`	This graph contains ADMS information on the project: see Project Data Stored as ADMS Graph. ADMS is a vocabulary used to describe semantic assets. See also: https://www.w3.org/TR/vocab-adms/
	Quality settings	`<<baseUrl>/<projectId>/thesaurus/qualitySettings>`	These graphs contain the project quality settings. See also: Define Quality Settings
	Notification settings	`<<baseUrl>/<projectId>/notification/settings>`	This graph stores information on the notification settings in the Approval Workflow.
	RDF Editor	`<<baseUrl>/<projectId>/metadata/rdfeditor>`	Stores the data of RDF edits created in the RDF Editor.
Default Graphs (Thesaurus Management)	Thesaurus data	`<<baseUrl>/<projectId>/thesaurus>`	This graph contains the data of concepts, concept schemes, collections and SKOS-XL labels.
	History data	`<<baseUrl>/<projectId>/thesaurus/history>`	This graph contains the history data related to all Graph Modeling actions. See also: Graph Modeling History
	URI settings	`<<baseUrl>/<projectId>/thesaurus/uriSettings>`	This graph stores the URI settings for a project. See also: URI Management - Overview
	Local users	`<<baseUrl>/<projectId>/thesaurus/users>`	Contains all local user profiles (excluding default user roles). For details refer to: Graph Modeling User Administration Setup Using Keycloak
Optional Graph (Projects)	Template configurations	`<<baseUrl>/<projectId>/configuration>`	Stores the definitions of templates for project export. After you have created a project export template, its metadata, such as creator, modification date, and configuration triples, appears here.
Optional Graphs (Thesaurus Management)	SKOS Notes	`<<baseUrl>/<projectId>/thesaurus/notes>`	This graphs contains SKOS change/editorial/history notes. See also: Adding Notes to your Concepts
	Workflow data	`<<baseUrl>/<projectId>/thesaurus/workflow>`	This graph contains the workflow data (state, assignee) of concepts or SKOS-XL labels. See also: Approval Workflow
	Deprecated resources	`<<baseUrl>/<projectId>/thesaurus/deprecated>`	This graph contains the information on deprecated/deleted resources such as concepts and concept schemes. See also: Deleting Concepts & Subtrees
	Quality management data	`<<baseUrl>/<projectId>/thesaurus/qualityReport>`	This graph contains the quality report data of the last report. See also: Create a Quality Report
	SPARQL lists	`<<baseUrl>/<projectId>/thesaurus/sparqllists>`	This graph contains information about all SPARQL lists created. See also: SPARQL Lists
	Batch linking data	`<<baseUrl>/<projectId>/thesaurus/linking>`	This graph contains all information on the last batch linking task. See also: Project Linking - Batch Linking
	Concepts added to the exclude-list	`<<baseUrl>/<projectId>/thesaurus/blacklist>`	This graph contains all concepts and terms added to the exclude-list. See also: Add Concepts and Terms to Exclude-list
	Linked Data	`<<baseUrl>/<projectId>/linkeddata/<ld-source>> e.g. <<baseUrl>/<projectId>/linkeddata/en/dbpedia>`	This graphs contain data copied from a linked data source. The name of the graph depends on the linked data sources used. See also: Linked Data Enrichment with Graph Modeling
	Categories data	`<<baseUrl>/<projectId>/linkeddata/categories>`	Linked data categories retrieved using the linked data feature will be stored in this graph.
Temporary Graphs (Data Validator & Reasoning)	Import linked projects data	`<<baseUrl>/<projectId>/thesaurus/import/projects>`	The imported project data will be stored in this graph. See also: Graph Modeling RDF Import & Export
	Import schema data	`<<baseUrl>/<projectId>/thesaurus/import/schema>`
	Import project metadata	`<<baseUrl>/<projectId>/thesaurus/import/metadata>`
	Reasoning schema data	`<<baseUrl>/<projectId>/thesaurus/reasoning>`
Optional Graphs (Corpus Management)	Candidate concepts	`<<baseUrl>/<projectId>/corpus/candidates>`	This graph contains candidate concepts that have been selected in the corpus analysis. See also: Candidate Concepts List
	Disambiguation	`<<baseUrl>/<projectId>/corpus/disambiguation>`	This graph contains the project disambiguation settings used for extraction. See also: Thesaurus Based Disambiguation of Annotated Concepts
Optional Graphs (Semantic Classifier)	Document classification	`<<baseUrl>/<projectId>/classification>`	The classification results for the trained classifiers will be stored in this graph. See also: Semantic Classifier - Overview
	Indexed documents	`<<baseUrl>/<projectId>/documents>`	This graph contains all documents uploaded during training and testing classifiers.

Please note that projectIDs used in graph URIs are textual project identifiers and not UUIDs. A textual identifier is generated during project creation as part of the URI generation process, which, along with the project’s base URI, forms the complete project URI. This URI can be found at the Triples tab after navigating to the project's details view. The image below shows that the URI http://server.com/ProjectExample consists of base URI (starting with "http:// ") and textual project identifier ProjectExample.

In this section: