--- title: http://graph.build/resource# — the default instance namespace description: The namespace Studio uses for instances. Hash IRIs already land here; slash forms are redirected to this page. --- [Skip to content](https://graph.build/resource#main) [![graph.build](https://graph.build/hubfs/raw_assets/public/graphbuild-theme/images/logo-secondary-reverse.svg)](https://graph.build/) Menu - Platform - AI context [Context for AI](https://graph.build/ai-context) [Semantic layer](https://graph.build/semantic-layer) [GraphRAG](https://graph.build/graphrag) [MCP & agent access](https://graph.build/mcp) [Ontologies explained](https://graph.build/resources/ontology) - Resources [Blog](https://graph.build/blog) [Graph fundamentals](https://graph.build/resources) [Documentation](https://graph.build/documentation) - Company [About us](https://graph.build/about) [Consulting](https://graph.build/consulting-services) [Contact](https://graph.build/contact) [Book a demo](https://graph.build/enquire/book-a-demo) Model [Studio](https://graph.build/graph-build-studio) [Visual graph modelling](https://graph.build/graph-modelling-tool) [Ontologies & vocabularies](https://graph.build/platform-architecture#ontology) Transform [Transformers](https://graph.build/graph-build-transformers) [Knowledge graph ETL](https://graph.build/knowledge-graph-etl) [Change data capture](https://graph.build/graph-build-transformers#cdc) Write [Writers](https://graph.build/graph-build-writer) [Database compatibility](https://graph.build/graph-databases) [Deployment](https://graph.build/platform-architecture#deployment) You are here [The graph engineering lifecycle](https://graph.build/knowledge-graph-building) Design, configure, engineer, iterate and automate graph model production: the whole lifecycle, without writing bespoke ingest code for each project. Model [Studio](https://graph.build/graph-build-studio) [Visual graph modelling](https://graph.build/graph-modelling-tool) [Ontologies & vocabularies](https://graph.build/platform-architecture#ontology) Transform [Transformers](https://graph.build/graph-build-transformers) [Knowledge graph ETL](https://graph.build/knowledge-graph-etl) [Change data capture](https://graph.build/graph-build-transformers#cdc) Write [Writers](https://graph.build/graph-build-writer) [Database compatibility](https://graph.build/graph-databases) [Deployment](https://graph.build/platform-architecture#deployment) AI context [Context for AI](https://graph.build/ai-context) [Semantic layer](https://graph.build/semantic-layer) [GraphRAG](https://graph.build/graphrag) [MCP & agent access](https://graph.build/mcp) [Ontologies explained](https://graph.build/resources/ontology) Resources [Blog](https://graph.build/blog) [Graph fundamentals](https://graph.build/resources) [Documentation](https://graph.build/documentation) Company [About us](https://graph.build/about) [Consulting](https://graph.build/consulting-services) [Contact](https://graph.build/contact) [Book a demo](https://graph.build/enquire/book-a-demo) http://graph.build/resource# # This is where the things themselves live When you create an ontology in Studio, instances — a specific person, a specific asset — are minted under this namespace unless you change it. The hash is deliberate. Everything after it stays in the browser, so every such address already resolves to this page. [The ontology namespace](https://graph.build/ontology) [Ontologies explained](https://graph.build/resources/ontology) Why the hash ## The identifier never leaves the address bar A hash URI is one document with many names inside it. The browser asks for /resource and keeps the rest locally. That is why there is one page here rather than one page per record, and why following a specific instance still lands you in the right place. the namespace ### Records, not the types they belong to http://graph.build/resource# is the default prefix for the things the vocabulary describes. person-1842, org-acme, asset-77 — the instances — are appended after the hash. The type of those things, Person or Organisation, lives under http://graph.build/ontology/. Splitting them is ordinary RDF practice: the schema can be published, versioned and reused without carrying every record with it, and the records can grow without rewriting the schema. The consequence: a graph you can show someone, and a vocabulary they can adopt, without handing them the contents of the database. resource# instances resource# instances person-1842 a Person org-acme an Organisation asset-77 an Asset contract-9 a Contract minted under http://graph.build/resource# The pair ## Two namespaces, because types and things are different Studio ships two defaults. One is for what things mean. The other is for the things themselves. Mixing them is how a graph becomes impossible to reuse. ### [http://graph.build/ontology/ The vocabulary. Classes, properties and the relationships between them. A slash namespace: each term is a path of its own, and following one lands on the ontology page. go to the ontology namespace](https://graph.build/ontology) ### http://graph.build/resource# The instances. A specific person, a specific asset. A hash namespace: everything after the hash stays in the browser, so this one page is already the destination. holds the records Ontologies in short ## The vocabulary names the types. This namespace holds the members. The longer version is the fundamentals guide. The three facts that matter for this namespace are these. ### [What an instance is A particular thing the ontology can talk about. Person is a class; person-1842 is one person. The class is reused. The instance is not. That distinction is the whole reason there are two namespaces. read ontologies explained](https://graph.build/resources/ontology) ### [Why it needs its own namespace If instances shared the vocabulary namespace, a record named Person would collide with the class Person. Keeping them apart means a term always means the same kind of thing, which is what lets an outside tool read the graph without a glossary. see vocabularies in Studio](https://graph.build/platform-architecture#ontology) ### You can change it The default is a starting point, not a lock-in. If the graph is yours, the namespace should be too — a domain you control. Change it in the project before other systems start citing the identifiers, because those citations do not update themselves. in Studio Next ## See how the instances get there Studio holds the types. Transformers mint the records from the systems you already run, under this namespace or under one you set. Forty-five minutes on your own data is the shortest way to see both fill in. [Book a demo](https://graph.build/enquire/book-a-demo) [See Studio](https://graph.build/graph-build-studio) - Mapped from sources you already have - Your namespace, or this default - No obligation to buy anything Platform [Studio](https://graph.build/graph-build-studio) [Transformers](https://graph.build/graph-build-transformers) [Writers](https://graph.build/graph-build-writer) [Database compatibility](https://graph.build/graph-databases) [Platform architecture](https://graph.build/platform-architecture) AI context [Context for AI](https://graph.build/ai-context) [Semantic layer](https://graph.build/semantic-layer) [GraphRAG](https://graph.build/graphrag) [MCP & agent access](https://graph.build/mcp) [Ontologies explained](https://graph.build/resources/ontology) Resources [Blog](https://graph.build/blog) [Graph fundamentals](https://graph.build/resources) [Choosing a graph database](https://graph.build/graph-databases) [How to build a knowledge graph](https://graph.build/knowledge-graph-building) [Documentation](https://graph.build/documentation) Company [About us](https://graph.build/about) [Consulting](https://graph.build/consulting-services) [Contact](https://graph.build/contact) Legal [Privacy policy](https://graph.build/privacy-policy) Get in touch No newsletter. If you want to talk about a model, or want to be kept posted, the contact form is the way in. [Contact us](https://graph.build/contact) - © 2026 Graph.Build · A trading name of Data Lens Labs Ltd, registered in England & Wales, company number 12483318 [![graph.build](https://graph.build/hubfs/raw_assets/public/graphbuild-theme/images/logo-secondary-reverse.svg)](https://graph.build/)