YAGO - Neo4j Mapping

YAGO is based on RDF
(Resource Description Framework), a family of specifications from the
W3C (World Wide Web Consortium).
RDF uses (subject, predicate, object) "triples"
which map fairly easily to Neo4j's nodes, properties, and relations.
However, there are also some significant differences.
So, a bit of structural and syntactic mapping may be appropriate.

Direct Mapping

The SPARQL Plugin for Neo4j maps each RDF triple
to a Neo4j relation, generating supporting nodes as needed.
Subjects and objects become nodes, with value and kind properties, eg:

This allows the plugin to support SPARQL in Neo4j,
but the encoding doesn't seem very convenient, let alone idiomatic.
There are also issues having to do with encoding efficiency,
handling of literal types, etc.

Idiomatic Mapping

Let's see if we can create an idiomatic mapping for YAGO
that is also convenient and efficient.
We'll start with first principles, then suggest accommodations...