Surprisingly, I could not find an Issue about this #DBpedia problem. Now there is one: https://github.com/dbpedia/extraction-framework/issues/820

Contrary to my initial guess of an extractor bug, further investigations made an SPARQL endpoint (#openlinksw #virtuoso) bug seem more likely.

Remarkably:
➡️ Despite the lack of #DBpedia types, equivalent #Wikidata types are present in DBpedia.
➡️ Not all resources are affected: e.g. https://dbpedia.org/page/John_Young_(astronaut) is typed as http://dbpedia.org/ontology/Astronaut.
➡️ Right and wrong typed astronauts have the astronaut infobox (which is properly mapped https://mappings.dbpedia.org/index.php/Mapping_en:Infobox_astronaut) on #Wikipedia.

I guess an extractor bug 🪲.

Side effect: Many astronauts are displayed as "animals". Although on might consider this as ontologically correct, it is quiet odd.

@dbpedia

With ABECTO 3.1.5, I restored regular pushes of space travel data deviations between #Wikidata and #DBpedia to https://mismatch-finder.toolforge.org @nightrose. But it provides (at first glance) strange results (🔗 https://mismatch-finder.toolforge.org/results?ids=Q107667|Q115651852), like:
➡️ John Young member of the crew of Apollo 16 mismatches http://dbpedia.org/resource/Apollo_16
➡️ SpaceX Crew-10 crew member Anne McClain mismatches http://dbpedia.org/resource/Anne_McClain

Reason: Missing http://dbpedia.org/ontology/SpaceMission, http://dbpedia.org/ontology/Astronaut, … type statements in @dbpedia.

An unconventional approach to avoid providing an email address in the User-Agent was chosen in #DBpedia by reusing the user agent of #curl: https://github.com/dbpedia/extraction-framework/commit/de3ca70694f347db84a2daeb88d8218506075f81
I proposed an alternative: https://github.com/dbpedia/extraction-framework/issues/819

@dbpedia @wikidata