Hi! Cool project. It reminds me I need to add schema:name to the real-world script

I'd like to know what the RDF looks like. Could I see an example?

Sure. docs.ttl.txt. You can also create this output with the example instructions. You don't need to have logseq installed

There are some similarities and differences between your example and this example script:

Looks like we can both create rdf triples at a page level and on parts of a page. Your note is what we'd call a block in logseq but block is more granular. Looks like you also have natural language properties within a note with is a :: which we don't have yet.
We reference the property urls differently. It looks like you're referencing them directly in the notes and shortening them with script prefixes. For my example with the docs graph, I alias that information once in the property's page e.g. https://docs.logseq.com/#/page/description . Click on url to see other properties that have the same structure. I did it this way to encode all the information in the graph/vault and try to make it user friendly.
I think your example uses a custom parser. My example is using logseq's parser so any concepts I rely on like properties are also supported within the app
One thing that may be interesting from the docs graph, is that every class, property or class instance is a page in the graph, which allows for the user to reference and navigate with them easily. Respective examples are in the linked refs of https://docs.logseq.com/#/page/Class, https://docs.logseq.com/#/page/Property and https://docs.logseq.com/#/page/Feature

linked-data example #5

Description