Picking the right Wikidata properties for heritage starts with P31 (instance of) to declare what the object is, then a small core of identity, provenance and location properties, with everything else added only when you have the data and a source. The reliable method is reuse: find three well-formed items of the same type and copy their property patterns rather than inventing. Choosing the wrong property — P170 where P50 belongs, or overloading an unrelated property — quietly breaks constraints and cross-collection queries.

How do I choose the foundational property, P31?

P31 (instance of) is the hinge of the whole item. It determines which constraints apply, which queries find your object, and how tools interpret it. Be specific but correct:

P31  Q87167      # manuscript
P31  Q3305213    # painting
P31  Q179700     # statue
P31  Q210272     # cultural heritage (use as broad class, not sole type)

Prefer the most specific accurate class. "Cultural heritage" alone is too broad to be useful; pair a specific physical type with subject or heritage-designation properties instead.

What is the core property set for any heritage object?

Most objects share a backbone. Learn these first:

Property	Meaning	Notes
P31	instance of	the object's class
P186	made from material	medium/material
P571	inception	date created, with precision
P170 / P50	creator / author	object vs text
P195	collection	holding collection
P217	inventory number	qualifier on P195
P276	location	current physical location
P1071	location of creation	where it was made

Fill the backbone before reaching for niche properties. A consistent core across a collection is more valuable than scattered rich detail on a few items.

Creator, author, or contributor — which applies?

This distinction matters and is easy to get wrong:

• P170 (creator) — visual and physical works: paintings, sculpture, artefacts, photographs.
• P50 (author) — textual works: books, charters, manuscripts as texts.
• P110 (illustrator), P1640 (curator), P1071 for production place — use the precise role.

If you only know the role loosely, use the broad property with a qualifier rather than guessing a specific one.

How do I find the right property when I am unsure?

Three reliable moves, in order:

1. Copy a good example. Open three high-quality items of the same type and note which properties they use.
2. Check the WikiProject. Heritage-relevant WikiProjects publish recommended data models.
3. Read the constraints. Each property page lists value-type and usage constraints that tell you whether it fits.

# What properties do existing manuscripts in a collection use?
SELECT ?prop (COUNT(*) AS ?n) WHERE {
  ?item wdt:P195 wd:Q12345 ; wdt:P31 wd:Q87167 ; ?p ?v .
  ?prop wikibase:directClaim ?p .
} GROUP BY ?prop ORDER BY DESC(?n)

This query literally shows you the community's de facto model for that type in that collection.

What about heritage-specific designations?

Listed-building and protected-status data have dedicated properties: P1435 (heritage designation) with a value like a national listing grade, plus the relevant register ID property for your country. Record the designation, its date with a qualifier, and a reference to the official register. These properties are what let researchers query "all Grade I listed buildings created before 1700" across the dataset.

What mistakes should I avoid when choosing properties?

• Overloading a convenient-but-wrong property instead of proposing a correct one.
• Using P170 for texts or P50 for objects.
• Treating "cultural heritage" as a complete P31 when a specific type exists.
• Adding rich niche properties while the core backbone is still incomplete.
• Inventing local conventions instead of reusing community models.

When in genuine doubt, the closest established property plus a clarifying qualifier beats a perfect-but-nonexistent one.

Key Takeaways

• P31 (instance of) is the foundational choice; be specific and accurate.
• Master a small core backbone before reaching for niche properties.
• Use P170 for objects and P50 for texts — match the property to the thing.
• Find the right property by copying good examples, checking WikiProjects and reading constraints.
• Record heritage designations with P1435 plus a register ID and reference.
• Reuse community models; never overload an unrelated property for convenience.

Frequently Asked Questions

Which property declares what a heritage object is?

P31 (instance of) declares the class, for example Q87167 manuscript, Q3305213 painting, or Q210272 cultural heritage. It is the single most important property to get right because constraints and queries depend on it.

How do I find the right property for a concept?

Search existing well-formed items of the same type and copy their property usage, browse the property catalogue, or check the relevant WikiProject. Reusing established patterns beats inventing your own.

What property records the holding institution?

P195 (collection) links to the collection item, and P276 (location) records physical location. Use P217 (inventory number) as a qualifier for the accession ID.

Should I use P170 or P50 for who made something?

Use P170 (creator) for visual and physical objects such as artworks and artefacts, and P50 (author) for textual works. Pick the one that matches the kind of thing.

What if the perfect property does not exist?

Use the closest established property with a clarifying qualifier, or propose a new property through the community process. Never overload an unrelated property just because it is convenient.

How do I know which properties are expected for a type?

Check the property constraints and the relevant WikiProject's data model, and look at how several high-quality existing items of that type are described.

Related reading

• Model heritage items in Wikidata
• How to Add references in Wikidata
• How to Get started with Wikidata for heritage
• Choose an RDF vocabulary
• Link entities to Wikidata