4 ms·

KG are cool, but I haven't find a practical framework of combining simple logical predicates with temporal facts (things that are true at a certain moment in ti

by wrnr 5y ago

KG are cool, but I haven't find a practical framework of combining simple logical predicates with temporal facts (things that are true at a certain moment in time) and information provenance (the truthiness of information given the origin). There might be ways to encode this information in a hyper graph but they are far from practical.

physicsyogi 5y ago
Checkout Datomic. It’s a temporal database that uses datalog as it’s query language. There’s also Datascript, which does the same thing.
- superlopuh 5y ago
  Unfortunate name for a product, I can't find anything called Dynamic on DDG, only dynamic things with a lowercase d. Do you have a link to the project?
  - bosie 5y ago
    not dynamic but Datomic
    - superlopuh 5y ago
      Dyslexic moment on my part, thank you
      - omginternets 5y ago
        Lysdexia makes fools of us all ;)
- simongray 5y ago
  ... there's a whole bunch of Datomic-likes these days: https://github.com/simongray/clojure-graph-resources#datalog https://github.com/simongray/clojure-graph-resources#datalog
mmarx 5y ago
Wikidata statements (which roughly correspond to the edges in the Knowledge Graph) have quite a bit of Metadata associated with them: they can have refer to sources that state this particular bit of knowledge, they have a so-called rank that allows distinguishing preferred and deprecated statements, and the can be qualified by another statement in the graph. Temporal validity is encoded using a combination of rank and qualifiers, as for, e.g., Pluto[0], where the instance-of statement saying that “Pluto is a planet” is deprecated and has an “end time” qualifier, and the preferred statement says “Pluto is a dwarf planet,” with a corresponding “start time” qualifier. In principle, all of this information is available through the SPARQL endpoint or as an RDF export (there is also the simplified export that contains only “simple” statements lacking all of that metadata), so reasoning over this data is not entirely out of reach, but the sheer size (the full RDF dump is a few hundred GBs) is also not particularly practical to deal with. [0] https://www.wikidata.org/wiki/Q339#P31 https://www.wikidata.org/wiki/Q339#P31
- pcrh 5y ago
  >Wikidata https://en.wikipedia.org/wiki/Wikidata https://en.wikipedia.org/wiki/Wikidata Thanks for that! TIL. It seems a fascinating project in epistemiology!
- ablekh 5y ago
  The size of Wikidata knowledge base / relevant graph (as well as Linked Open Data Cloud KBs and other large KBs) certainly presents some challenges. However, I think that the largest challenge and, in fact, the main obstacle, for practical programmatic solutions is the use of essentially meaningless alphanumeric identifiers assigned to entities and properties. All corresponding identifiers need to be discovered first manually in order to construct relevant SPARQL queries. Needless to say that these queries are not particularly human-readable (or, rather, human-interpretable) as well.
  - tuukkah 5y ago
    Why manually, when you have APIs to find Wikidata items and properties based on their labels, descriptions, aliases, data, metadata and use? If you mean autocomplete UI or tooltips, look no further than the query editor and its Ctrl+Space at https://query.wikidata.org/ https://query.wikidata.org/
gballan 5y ago
Might be worth looking at Sowa's Conceptual Graphs. E.g., [1], talks about time, and links to his book. [1] http://www.jfsowa.com/ontology/process.htm http://www.jfsowa.com/ontology/process.htm
hocuspocus 5y ago
Check out Nexus, which was designed with versioning in mind, that solves this kind of challenge at the Blue Brain Project: https://bluebrainnexus.io/ https://bluebrainnexus.io/

by wrnr 5y ago

physicsyogi 5y ago

Checkout Datomic. It’s a temporal database that uses datalog as it’s query language. There’s also Datascript, which does the same thing.

superlopuh 5y ago
Unfortunate name for a product, I can't find anything called Dynamic on DDG, only dynamic things with a lowercase d. Do you have a link to the project?
- bosie 5y ago
  not dynamic but Datomic
  - superlopuh 5y ago
    Dyslexic moment on my part, thank you
    - omginternets 5y ago
      Lysdexia makes fools of us all ;)
simongray 5y ago
... there's a whole bunch of Datomic-likes these days: https://github.com/simongray/clojure-graph-resources#datalog https://github.com/simongray/clojure-graph-resources#datalog

mmarx 5y ago

Wikidata statements (which roughly correspond to the edges in the Knowledge Graph) have quite a bit of Metadata associated with them: they can have refer to sources that state this particular bit of knowledge, they have a so-called rank that allows distinguishing preferred and deprecated statements, and the can be qualified by another statement in the graph. Temporal validity is encoded using a combination of rank and qualifiers, as for, e.g., Pluto[0], where the instance-of statement saying that “Pluto is a planet” is deprecated and has an “end time” qualifier, and the preferred statement says “Pluto is a dwarf planet,” with a corresponding “start time” qualifier. In principle, all of this information is available through the SPARQL endpoint or as an RDF export (there is also the simplified export that contains only “simple” statements lacking all of that metadata), so reasoning over this data is not entirely out of reach, but the sheer size (the full RDF dump is a few hundred GBs) is also not particularly practical to deal with. [0] https://www.wikidata.org/wiki/Q339#P31 https://www.wikidata.org/wiki/Q339#P31

pcrh 5y ago
>Wikidata https://en.wikipedia.org/wiki/Wikidata https://en.wikipedia.org/wiki/Wikidata Thanks for that! TIL. It seems a fascinating project in epistemiology!
ablekh 5y ago
The size of Wikidata knowledge base / relevant graph (as well as Linked Open Data Cloud KBs and other large KBs) certainly presents some challenges. However, I think that the largest challenge and, in fact, the main obstacle, for practical programmatic solutions is the use of essentially meaningless alphanumeric identifiers assigned to entities and properties. All corresponding identifiers need to be discovered first manually in order to construct relevant SPARQL queries. Needless to say that these queries are not particularly human-readable (or, rather, human-interpretable) as well.
- tuukkah 5y ago
  Why manually, when you have APIs to find Wikidata items and properties based on their labels, descriptions, aliases, data, metadata and use? If you mean autocomplete UI or tooltips, look no further than the query editor and its Ctrl+Space at https://query.wikidata.org/ https://query.wikidata.org/

gballan 5y ago

Might be worth looking at Sowa's Conceptual Graphs. E.g., [1], talks about time, and links to his book. [1] http://www.jfsowa.com/ontology/process.htm http://www.jfsowa.com/ontology/process.htm

hocuspocus 5y ago

Check out Nexus, which was designed with versioning in mind, that solves this kind of challenge at the Blue Brain Project: https://bluebrainnexus.io/ https://bluebrainnexus.io/