Which critical assets have no owner recorded?

31 assets. All 31 are classified CRITICAL and all 31 have an empty owner field. Twenty two of them sit in PROD-CORE-VLAN-100.

asset_idasset_namenetwork_segmentlast_review_date
ASSET-STO-0067SAN Frame MuenchenDR-VLAN-4002024-11-02
ASSET-DB-0233Kartenzahlung DB ReplicaPROD-CORE-VLAN-1002025-06-14
ASSET-NET-0104Core Switch Stack BPROD-CORE-VLAN-1002023-09-30

3 of 31 shown.

Where the answer came from
Entity ict_asset_inventory, bound to itsm_prod.SYS_INVENTAR
Filter criticality_classification = CRITICAL
Value map KRITISCHCRITICAL, accepted by a human on 2026-09-08
Filter owner is null
Column itsm_prod.SYS_INVENTAR.VERANTW, 7 percent null across the table
The query it actually ran
select ict_asset_inventory where criticality_classification = CRITICAL and owner is null return asset_id, asset_name, network_segment, last_review_date

Written in entities and fields, not tables and columns. The binding turns it into SQL, so a rename in the source breaks the binding rather than the question.

Which of our critical functions depend on a single provider?

Partly. 214 critical functions are bound, from the spreadsheet rather than from a system. Of those, 131 resolve to named assets and 3 of the 131 depend on a provider with no second source.

Read this with the coverage in mind The link from a function to its systems is free text in that spreadsheet, and it resolves for 61 percent of rows. The other 83 functions are not covered by this answer, and I cannot tell you whether they are single sourced or not.
Where the answer came from
Entity critical_function_register, bound to Kritische_Geschaeftsprozesse_2026.xlsx
Sheet Prozesse 2026, range A2:I215, accepted by a reviewer on 2026-09-08
Join Betroffene Systeme → SYS_INVENTAR.BEZEICHNUNG by name, 61 percent resolve
Then ict_third_party_register, one provider per asset, count of distinct providers

The suggested question is the interesting one: it looks answerable, and it is not.

Why the refusals matter more than the answers

An assistant over a warehouse can always produce something. The value of a bound ontology is that it knows the difference between a field that is empty and a field that does not exist, so it can decline the second case instead of quietly answering a nearby question. Every refusal above names the missing binding, which turns a wrong answer into a work item.