> For the complete documentation index, see [llms.txt](https://learn.coremodels.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.coremodels.io/user-guides/json-ld/json-ld-type-property.md).

# JSON-LD @type property

CoreModels applies this translation to any import type and handles the '@type' property accordingly. '@type' is a special property that determines how a JSON-LD object is imported as either a type, element, or a taxonomy in CoreModels.

This is based on how the schema.org importer is originally designed according to the [rdfs definition](http://www.w3.org/2000/01/rdf-schema).

If "@type" is set to "rdfs:Class", then it's a type. Here is the code from our [sample file](https://drive.google.com/file/d/1HK_jbHpmHEXo0BizQMDt4E0EHuZXttUN/view).

```
{ 
  "@id": "sampleType1",
  "@type": "rdfs:class",
  "rdfs:comment": "This is a sample json-ld object that will be considered 
     a type due to having the rdfs:class value in the @type property",
  "rdfs:label": "Sample Type 1",
  "isrequired": "sms:true"
}
```

Once CoreModels proceeds the import, the type will be created with its label Sample Type1.

<figure><img src="/files/JC5c32hrWMeWPMDu0HZ9" alt=""><figcaption><p>Types Grid - Sample Type 1</p></figcaption></figure>

If "@type" is set to "rdf:property", then it's an element.

```
{ 
  "@id": "sampleElement1",
  "@type": "rdf:property",
  "rdfs:comment": "This is a sample json-ld object that will be considered 
     an element due to having the rdf:property value in the @type property, 
     it will also connect to sampleType1 due to having the domainIncludes",
  "rdfs:label": "Sample Element 1",
  "schema:domainIncludes": [{
    "@id" : "sampleType1"
  }],
  "isrequired": "sms:true" 
}
```

'sampleElement1' is has a 'domainIncludes' relation to 'sampleType1', therefor it'll appear in the Elements grid of 'Sample Type 1'.

<figure><img src="/files/KVSyZ6z4eUKF1bnaY1Wo" alt=""><figcaption><p>Types Grid - Sample Type 1 with Sample Element 1</p></figcaption></figure>

If "@type" is set to "rdfs:Class" AND "rdfs:subClassOf" has "schema:enumeration", then it's a taxonomy.

```
{ 
  "@id": "sampleTaxonomyParent",
  "@type": "rdfs:Class",
  "rdfs:comment": "his is a sample json-ld object that will be considered a taxonmy
     due to having the rdfs:class value in the @type property
     AND the schema Enumeration in the subClassOf",
  "rdfs:label": "Sample Taxonomy Parent",
  "rdfs:subClassOf": [{
    "@id" : "schema:enumeration"
  }],
  "isrequired": "sms:true"
}
```

<figure><img src="/files/b4TkslQXaHjex0MJ0dm4" alt=""><figcaption><p>Taxonomies Grid - Sample Taxonomy Parent</p></figcaption></figure>

If "@type" is set to any previous taxonomy, then it's a child of that taxonomy.

```
{
  "@id": "sampleTaxonomyChild",
  "@type": "sampleTaxonomyParent",
  "rdfs:comment": "his is a sample json-ld object that will be considered 
     a taxonmy due to having the sampleTaxonomy Parent value in the @type property
     it will be set by default to be the child of that taxonomy",
  "rdfs:label": "Sample Taxonomy Child",
  "isrequired": "sms:false"
}
```

CoreModels will automatically establish a relationship between the child taxonomy and 'Sample Taxonomy Parent', thereby creating parent-child relation. Here's how the child taxonomy will look like.

<figure><img src="/files/niyVLNQ7GWwtLx7FBwpz" alt=""><figcaption><p>Taxonomies Grid - Parent Child relation</p></figcaption></figure>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.coremodels.io/user-guides/json-ld/json-ld-type-property.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.