Most recents (5)

I’ve been testing out #ChatGPT regarding its capabilities with #RDF, #SPARQL, #SHACL and #KnowledgeGraphs in general.

Here’s a short thread about how you can use it to generate RDF graphs, SHACL restrictions and SPARQL queries.

Step 1: Asking it to generate a SHACL shapes restriction for a random domain: tinyurl.com/5en9uc7k

Step 2: Asking it to extend the SHACL example with restrictions about the actor(s) of the movie: tinyurl.com/4hk588nf

Read 5 tweets

Kingsley Uyi Idehen

@kidehen

You can't keep a good thing down.

#LinkedData is a classic example, despite confusion that has swirled around it for years.

I was watching @timberners_lee's @TEDTalks presentation on the subject earlier today, and it has aged very well.

#Web30

🧵

@YouTube

#LinkedData principles add a powerful dimension to #StructuredData creation, courtesy of a #Hyperlink functioning as an unambiguous Entity Name.

Here's a @YouTube video titled "How the hyperlink changed everything" about this "deceptively simple" tool.

Once you the power of #LinkedData settles in, its importance to #KnowledgeGraph creation becomes clearer.

Here's a nice explainer video.

#SemanticWeb #Web30

Read 7 tweets

Pavel Klinov

@klinovp

i wonder how many people who know something about "usual" complexity stuff, eg big-O, common time/space compl. classes like P/NP or PSPACE, have heard about enumeration complexity, eg delays. Because it's extremely useful when it comes to query languages, esp. on graphs. 1/

massively simplifying, the "usual" complexity stuff is going to tell you how much time or memory your query engine may use (in worst case) for query/data of some size. Great, but not the whole story. 2/

It's not going to tell you i) how long you may need to wait till 1st result, ii) how long you may need to wait *between* results. That, however, makes huge difference to clients in practice. 3/

Read 9 tweets

Ash_Crow

@ash_crow

https://twitter.com/Hazukashi1/status/1061915969558327296

Alors, cette carte est tirée des batailles enregistrées dans #Wikidata qui ont une date et une géolocalisation. C'est plus dense sur l'Europe parce que c'est moi qui ait commencé à ajouter ces deux infos systématiquement et que j'ai commencé par l'Europe.

https://twitter.com/Hazukashi1/status/1061915969558327296

Pourquoi j'ai fait ça ? Parce que j'avais besoin d'une liste de batailles du Moyen-Âge occidental pour debunker une autre discussion du même tonneau, et qu'après j'ai eu la flemme de finir les 10000+ batailles qui ont une entrée mais pas ces deux infos.

Ensuite, les batailles qui ont une entrée (même vide) sur Wikidata sont celles qui ont un article sur Wikipédia (toutes versions confondues). Dont le biais occidentalo-centré est connu (huit des dix plus grosses sont dans des langues européennes.)

Read 6 tweets

Kingsley Uyi Idehen

@kidehen