Ontology materializer
Persist a mapped fact set to a supported ontology store
This node writes ontology facts using a project package and a workspace ontology-store endpoint, such as Postgres or Apache Jena. It consumes an ont-fact-set from mapping rather than treating ordinary records as already valid ontology facts.
Before using it
Create or select the real resources described above in the pipeline’s project/workspace, inspect the upstream data shape and ensure your actor can perform this operation. A configuration fragment cannot create those resources. Read First pipeline for a complete graph and fixture.
Fields and bindings
| Field | Meaning |
|---|---|
packageId | The ontology package governing the facts |
dataEndpointId | Workspace Materialization endpoint using ontology_fact_store |
inputs | The connected fact-set output |
mode / atomicity | Declared materialization mode and transaction/per-unit behavior |
validation | Unknown terms, invalid records, cardinality and datatype handling |
conflictPolicy | Property-specific strategy and source priorities |
Configure
Prepare the ontology materializer node for the selected test resources. Use the operation and fields shown in this example. Show actual resource bindings, upstream/downstream ports and any write/model effects before applying the draft.Choose the compiled package and fact-store endpoint, connect the mapping fact port, and inspect validation/conflict fields. Use the store’s actual supported modes; serialized choices do not expand the adapter implementation.
Put this section under ontologyMaterializer on a full node of kind ontology_materializer. It is not a standalone API or MCP request. Replace resource placeholders, and provide the full node ports/policy and graph edges.
{
"packageId": "<PACKAGE_UUID>",
"dataEndpointId": "<FACT_STORE_ENDPOINT_UUID>",
"inputs": {
"facts": "order_facts"
},
"mode": "upsert",
"atomicity": "transactional",
"validation": {
"unknownTerms": "reject_fact_set",
"invalidRecords": "reject_fact_set",
"cardinality": "enforce",
"datatype": "enforce"
}
}Verify a bounded run
Check materializer results, rejected/quarantined data and ontology readback via a binding/query against this package/store. Two successful mapping rows alone do not prove persisted facts.
Validate, save a version and run a small known fixture. Inspect the actual node result and downstream consumer, not only the graph preview.
Limits and failure behavior
The endpoint’s fact-store capability differs from raw-table write. Effective atomicity and conflicts depend on the adapter. A store endpoint does not create the ontology definition or automatically establish every read binding.