I am currently building a query about Writers.
And I am trying to deal with the range of property “Occupation”.
I have found that “PersonFunction” is a reasonable range for “Occupation”.
But while having a look at some objects of the “Occupation” property, that are NOT of type
“PersonFunction”, I have found some weird things.
For example, the resources “Actor” and “Author” are only of type “Thing”, not of type “PersonFunction”.
the resources “Art_historian” and “Book_reviewer” are of types “Thing” and “Book” (???), but not of type “PersonFunction”.
“Biographer” is of type “Thing” and “Person” (???). But not of type “PersonFunction”
Etc.
I can agree that the occupation of a Writer (or more generally the occupation of a Person) can be many classes more than just PersonFunction. It could be:
yago:Activity100407535
yago:Duty100719494
yago:Function100720565
yago:Occupation100582388
But my question is this:
how to discuss proper type hierarchy in DBPedia?
And more important: what process should be enabled to update the type hierarchy (and the types of resources in general)?
To achieve agility, however, we envision the Databus to hold many other ontologies by DBpedia sub-communities. One example is this here: https://databus.dbpedia.org/propan/lhd/linked-hypernyms/2016.04.01
This is a classification built by the Czech DBpedia. It is automated, so once we get the abstract/text extraction going, it will pump out updated hypernym classifications/hierarchies.
So in my opinion, if you really want to have a good model for occupation, start a subproject and release it on the Databus, either free like “propan/lhd” and we might integrate it into core from there or paid (support in preparation).
Professions/occupations such as Arti historian, Book reviewer, Biographer etc typically don’t have infoboxes. DBpedia types are mostly assigned by infoboxes (though datasets like Heuristic Types and LHD assign extra types not based on infoboxes).
AFAIK, there is no infobox that generates the class PersonFunction directly. Instead, that class is used as an intermediate node when RDFizing Person boxes that include many positions/occupations over time (thin politicians and sports players who may change positions and teams many times over their life).
The two examples have an entity type [CitiesInIraq] or [historic place] which does not appear in the ontology.
So the question is: why are these types not listed in the mappings? Or can we find one of the mapping entry within these pages. I would expect having a type [City], subset of [Settlement] for the first example.
Thank you for your quick answer, and apologies for my (much) slower one. That is very helpful.
Yes I would be interested in having access to the mapping wiki, my user name is the same: AnthonyM598
One more question: how do you get the dbpedia entity type from a SPARQL query? Sorry for these questions, I am a beginner in the SPARQL / DBpedia universe.
Uganda (Wikidata ID: Q1036) is currently under the ontology class “musical artist”. How is this possible. I have wikipedia and the infobox is of type “Country”
world war (Wikidata ID: Q103495) under the class “military person”
Foreign relations of Pakistan (Wikidata ID: Q1063596) under the class “musical artist”
“Freedom of Information Act” (Wikidata ID: Q1003780) under the class “political party”