Inspect Concept
inspect_conceptGet a comprehensive semantic profile of a concept from schema.gov.it, showing its hierarchy, own and inherited properties, and usage data, with both asserted and effective views.
Instructions
Get a comprehensive profile of a concept from schema.gov.it, with explicit raw vs effective views.
Args:
uri: URI of the concept to inspect
mode: "raw" | "effective" (default: "effective")
source: "schema" | "local" | "hybrid" (default: "schema")
file_path / content / upload_id: local context when source="local" or source="hybrid"
lang: "it" | "en" | "any" (default: "any")
Tip: Use search_concepts first if you do not know the URI.
mode: "raw" — only explicitly asserted triples:
definition: literal annotations (label, comment, definition…)
hierarchy: direct type, parent classes (rdfs:subClassOf / skos:broader), child classes
usage: instance count
own_properties: properties with rdfs:domain exactly this class
mode: "effective" (default) — full OWL/RDFS-implied view, adds:
inherited_properties: properties from ancestor classes via rdfs:subClassOf+/skos:broader+, each row annotated with the ancestor that declares domain (distinguishes asserted-on-this-class from inherited)
incoming: properties pointing to instances of this type (data-level)
outgoing: properties used by instances of this type (data-level)
Interpreting own vs inherited:
own_properties = rdfs:domain written explicitly for this class → if missing, the property may still apply via inheritance
inherited_properties = rdfs:domain written on an ancestor → redundant to re-assert on this class unless restricting range
A property absent from both may still apply via owl:restriction, owl:equivalentClass, or owl:unionOf/intersectionOf (not shown — use query_sparql for those cases)
Limitations of effective mode:
owl:equivalentClass: not expanded (equivalent classes share all properties but this tool shows only the rdfs:subClassOf chain)
owl:unionOf / owl:intersectionOf: not traversed (anonymous class expressions)
owl:imports: schema.gov.it resolves these server-side; the endpoint already includes imported triples
Hybrid mode:
source="hybrid" uses the local/uploaded ontology as the base graph
for effective mode it enriches missing inherited properties and labels from schema.gov.it when ancestor URIs are known locally
it does not create a fully unified graph and does not resolve arbitrary owl:imports chains
When to use this vs X:
vs
inspect_local_concept: use this for concepts already in the remoteschema.gov.itcatalog; useinspect_local_conceptfor a local/uploaded ontologyvs
describe_resource: use this for a semantic profile (hierarchy, inherited properties, usage); usedescribe_resourcefor the raw RDF dump of a resourcevs
query_sparql: use this when you want the standard profile of one concept; usequery_sparqlonly for custom questions not covered here
All queries run in parallel for performance.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uri | Yes | The URI of the concept to inspect | |
| lang | No | Preferred label language; "any" keeps all languages. | any |
| mode | No | "raw": only asserted triples (own_properties, no ancestor traversal). "effective" (default): adds inherited_properties via rdfs:subClassOf+/skos:broader+ and data-level incoming/outgoing. | effective |
| format | No | RDF content type for inline content | |
| source | No | Execution context: "schema" for schema.gov.it, "local" for a local/uploaded ontology, "hybrid" for local base + schema.gov.it enrichment. | schema |
| content | No | Inline RDF content when source='local' or 'hybrid' | |
| file_path | No | Absolute path to a local ontology file when source='local' or 'hybrid' | |
| upload_id | No | Uploaded ontology store ID when source='local' or 'hybrid' |