Inspect Property in Local / Uploaded Ontology

Get the full semantic profile of a property from a local or uploaded ontology, resolving inherited domain and range via rdfs:subPropertyOf+.

CRITICAL — file access workflow:

1. Try file_path first (works only if the file is readable by the MCP server process).

2. If file_path fails for any reason → call get_upload_instructions with the local path, execute the returned curl command via Bash tool, parse the id from the JSON response, then call this tool again with upload_id.

3. NEVER read the file content and pass it through the conversation. NEVER attempt to parse or analyse the TTL text manually. The upload workflow sends raw bytes directly from disk to server without the AI ever seeing the content — it is always faster, cheaper, and more reliable.

Quale modalita di input usare:

• stdio / stessa macchina → file_path

• server remoto, file grande → get_upload_instructions + upload_id

• server remoto, file piccolo (<1 MB) → valuta content + format con inspect_local_ontology, poi passa a upload se servono query ripetute

Tip: Use search_concepts first if you are checking whether an equivalent property already exists in schema.gov.it. Use this tool only after you know you want to inspect the local/uploaded ontology.

Returns:

• definition: direct attributes from the local store (type, label, comment, subPropertyOf, inverseOf, functional flags)

• assertedDomain: rdfs:domain declared directly on this property in the local file

• assertedRange: rdfs:range declared directly on this property in the local file

• superproperties: ancestor chain via rdfs:subPropertyOf+; each entry has source:

  • "local" = found in the local store

  • "remote" = not in local file, resolved from schema.gov.it

  • "not-found" = absent from both

• inheritedDomain: domain values collected from super-properties, each annotated with ancestor URI and source

• inheritedRange: range values collected from super-properties, each annotated with ancestor URI and source

• effectiveDomain: deduplicated union of assertedDomain + inheritedDomain

• effectiveRange: deduplicated union of assertedRange + inheritedRange

• redundancy_analysis: diagnostic view of each asserted value:

  • "redundant": identical to an inherited value — the axiom can be dropped without semantic loss

  • "specialization": a rdfs:subClassOf of an inherited value — genuinely narrows the domain/range

  • "new": not present in any inherited value — adds information not implied by the super-property chain

• summary counts per category for quick overview

• warnings: super-properties not resolved, remote lookup failures

owl:imports handling: The local store typically does NOT contain imported ontologies (owl:imports declarations are not followed automatically). Super-properties from external namespaces (e.g. l0:name, l0:description from OntoPiA) are resolved against schema.gov.it automatically, making the effective semantics complete without requiring the full import chain to be loaded.

Use case — subproperty chains: For properties like ha_cup_collegato_per_fusione rdfs:subPropertyOf ha_cup_collegato, this tool shows whether domain/range are asserted directly, inherited from ha_cup_collegato, or need remote resolution. For subPropertyOf l0:name, it fetches l0:name's domain/range from schema.gov.it and shows it as source "remote".

When to use this vs X:

• vs get_property_details: use this for a local or uploaded ontology; use get_property_details for a property already published in the remote schema.gov.it catalog

• vs query_local_ontology: use this when you want the standard semantic profile of one property; use query_local_ontology only for custom SPARQL questions not covered here

Unicode SPARQL note: oxigraph rejects prefixed names with non-ASCII local parts. For properties with Unicode in the local name (e.g. myont:modalità_cup), always pass the full URI in angle brackets (<https://...#modalità_cup>).