Before a Knowledge Graph, Agree What the Business Means

Separate the meanings that change the customer response

Consider a hypothetical industrial service provider. All identifiers, contractual conditions and expected responses below are invented design assumptions, not a reported engagement or measured result. This is a separate scenario from the amendment-recovery example in the Enterprise Knowledge Backbone. Here, the relevant terms are available; the faulty mapping is the problem.

Customer C210 is party to agreement SC42, effective throughout 2026. Entitlement E7 defines the service benefit for asset P610. Assume the authorized contract specialist has confirmed that the complete applicable terms allow service requests at any hour, but include repair labor only when repair starts from 08:00 inclusive to 18:00 exclusive in the asset site’s local time. No other exception applies. These are hypothetical contractual interpretations, not general rules about service agreements.

Service event S88 records a repair starting at 19:30 on October 16, 2026. The customer-system field “covered” means agreement active. Mapping M1 incorrectly converts that field into “labor included.” The expected correction is to preserve agreement status and service eligibility while recommending that this labor is excluded from the agreed price. Assistance is limited to Recommend. The authorized person retains the customer commitment. An exclusion recommendation does not authorize a charge.

The minimum model connects Customer to Agreement, Agreement to Entitlement, and Entitlement to Asset. Service event identifies the requesting Customer and affected Asset and is assessed against the applicable Entitlement. Each concept needs a shared identifier or an explicit cross-system identifier mapping. The relevant links need their own scope and effective dates.

Keep references to the customer master, asset register, signed agreement and provision, and service-event record, including versions and the repair-start timestamp and time zone. Agreement status, eligibility to request service and labor inclusion remain separate outputs. Request time must not silently substitute for repair-start time.

A missing start time is a missing fact. A disagreement over what the contract means belongs with the authorized commercial or legal specialist. Different uses of “covered” can remain legitimate when each is named and mapped explicitly. The Knowledge owner coordinates that agreement with functional owners; the role does not itself confer authority to interpret contracts.

Prove what clearer meaning changes

Approve mapping M2 and its conditions before comparing technologies. Replay the same evidence through M1 and M2 in the existing service. These are proposed acceptance tests, not test results. For the first three rows below, identity and applicable terms are established.

For the unresolved case, the Operating owner assigns the maintenance-record owner to establish the start time, or the asset-record owner to resolve identity. The recommendation states the missing evidence and named next owner. An authorized service representative sets the customer’s response expectation. If resolution or qualified backup is unavailable, the affected disposition stays held in an owned queue. Unrelated work continues within its authority.

This first comparison isolates the value of corrected meaning. Reduced disputes or review effort are benefits to test through accepted customer outcomes and follow-up, not benefits to assume from the corrected label.

Record where the meaning is used

Change-impact analysis needs a maintained dependency trail. Definition record D1 describes the three meanings. Mapping M2 implements them in labor rule L2. The service-response and billing-recommendation workflows record that they consume L2. Each recommendation records the rule, mapping, definition and source versions actually used, alongside its service-event identifier.

The Knowledge owner maintains definition and mapping approvals. The Technology owner maintains the rule and consumer links with the Operating owners responsible for those workflows. They update the trail when a consumer is added, changed or retired. This can be a dependency table in existing systems or relationships in a graph. Neither discovers unrecorded dependencies automatically.

For this correction, follow the recorded links to identify consumers to update and earlier recommendations to review. Verify each consumer uses M2, then replay changed, unchanged and unresolved cases. Include status-only checks as controls against unintended change. If version records are incomplete, widen the review cohort and record that uncertainty. Historical customer commitments require separate authorized review; replaying them does not authorize a charge, refund or record change.

Compare design choices without making them a ladder

A glossary, a domain model, storage and retrieval answer different questions. They can be combined in several ways.

The credible simpler option is a maintained glossary and model, explicit field mappings, existing customer and service systems, relational entitlement rules, and a registered consumer list. It can produce the same recommendation and impact list. A diagram of connected concepts does not require a graph database.

Give that option and the graph the same approved definitions, identifiers, sources, dependency records and expected answers. Necessary modeling, stewardship, evidence repair and evaluation are shared work. Do not give only the graph clean inputs, or attribute the value of resolving “covered” to graph technology.

Estimate implementation-specific work separately. The relational option needs integration, joins, indexes and rule maintenance, but may reuse established skills and support. The graph option needs relationship loading or federation, query development, integration and reconciliation with authoritative systems, plus graph-specific skills and support. Either may require additional infrastructure. Compare actual effort and recurring costs; neither architecture is inherently free of maintenance.

GraphRAG adds another choice. Microsoft’s original approach uses a model-derived graph and community summaries to answer broad questions across document collections. Its reported evaluation concerns those questions, not this entitlement decision. [4] This example can use structured queries without GraphRAG. Any generated explanation still needs evidence and output evaluation. NIST recommends checking sources, citations and retrieval grounding. [5] Graph structure alone establishes neither truth nor permission nor reliable AI output.

Ask which additional relationship work earns the investment

A stronger graph case might emerge when several contract families, shared definitions and changing consumers make impact questions frequent and varied: which recommendations used a disputed mapping through an indirectly dependent rule, and which remain governed by different terms? Both implementations must answer from the same recorded relationships. Test whether the graph makes those questions materially easier to express, maintain or answer.

Request a bounded comparison using representative cases, cases reserved from tuning, realistic volumes and a deliberate mapping change. Agree the expected affected set and unaffected controls independently. Evaluate missed dependencies, false inclusions, correct unresolved responses, evidence traceability, update propagation, response time and human review effort. Include maintenance effort when a relationship or rule changes. A faster traversal that misses a consumer is not a successful result.

Keep one-time build costs separate. Compare Cost per accepted outcome for a matched cohort and period: total recurring operating cost divided by outcomes the Outcome owner accepts after the agreed follow-up. Here, acceptance requires an authorized customer response supported by applicable evidence and sustained through that follow-up; unresolved cases remain outside the count. Include technology, review, correction, exceptions, support and recovery; failed or repeated attempts add cost, not accepted outcomes. With zero accepted outcomes, report “not calculable.” Released capacity becomes cash savings only when expenditure changes.