Live webinar Nov 5: save your seatLive webinar Nov 5: Building Golden Records & Entity Resolution with Fluree. Save your seat
Fluree AI · Model
One vocabulary, every system.
Build, review and publish the taxonomies and ontologies your data and AI depend on, in one workspace for taxonomists and domain experts. Each system keeps its own terms; Fluree maps them to one governed concept and publishes it to the graph.
Every system names things its own way. The CRM has accounts, the ERP has clients, billing has customers, and three editorial teams tag the same topic three different ways. People reconcile that in their heads. An agent can’t.
The usual fix is a spreadsheet of terms, a wiki and the two people who remember why a term changed. It works until a term changes, and then nothing downstream finds out.
Fluree makes the vocabulary a governed asset. Experts edit it visually, every change goes through review before it’s official, and every version is kept. Published terms flow into FlureeDB, so document tagging and table classification run against the same concepts.
Ten things a spreadsheet of terms can’t do.
Taxonomies vs ontologies, a short guide- 01Visual modelingTree view, whiteboard mode and search-first bulk editing, so taxonomists shape the model without writing a query.
- 02Review before it’s officialMaintenance and candidate workflows. Reviewers compare stable and modified versions and approve or reject in bulk.
- 03Every version keptVersions live side by side, every create, update and delete is logged with who and when, and any two versions can be diffed.
- 04Crosswalks between vocabulariesTyped, scored mappings link overlapping terms across teams, so nobody has to merge taxonomies on day one.
- 05Relationships that match the businessPreferred and alternative labels, broader and narrower terms, equivalence mappings and polyhierarchies.
- 06Every languageLanguage-tagged labels and notes keep one concept consistent across every locale your teams work in.
- 07The model drives the appAdd a class or property and the forms, REST schemas, validation rules and import templates follow.
- 08Rules checked at entryPatterns, cardinality, required fields and naming conventions are enforced before anything saves; sweeps catch orphans, cycles and missing labels.
- 09Standards in, standards outSKOS, RDF, OWL and ISO 25964. Imports from RDF, SKOS and Excel with a guided mapper; exports to Excel, CSV, RDF, SKOS, OWL, XML, PDF and HTML.
- 10Publishes to the graphVocabularies flow to FlureeDB, steer what Fluree pulls from documents and how it classifies tables, and reach other systems through APIs.
Vocabularies that carry real systems.
Published deployments where a governed vocabulary does the heavy lifting. The numbers are from the published case studies.
All case studiesModel. Review. Publish.
From taxonomy to governed ontology- Model
- Taxonomists build terms, relationships and labels visually, in the language the business already uses.
- Review
- Changes queue for approval. Nothing becomes official without a reviewer and a record.
- Publish
- Approved vocabularies flow to the graph and to the pipelines that tag and classify against them.
Your cloud
Fully containerized in AWS, Azure or GCP, signed in through your own identity provider.
Managed by Fluree
A dedicated environment for your organization, with no shared tenant data paths.
Inside Fluree AI
Vocabularies publish to FlureeDB and steer document extraction and entity resolution; APIs and read-only portals serve everything else.
Taxonomy and ontology management comes with Fluree Enterprise, the enterprise tier of Fluree AI. Pricing depends on how and where you deploy it, and sales will walk you through it on a first call.
Put it on your vocabulary.
Bring a taxonomy, even a spreadsheet, and a second system’s terms. We load both, map them to one governed concept set, and show you the result in the graph.
