Architecture for Social Graph data that has a Time Frame Associated?

I am adding some “social” type features to an existing application. There are a limited # of node & edge types. Overall the data itself is relatively small (50,000 – 70,000 for each type of node) there will be a number of edges (relationships) between them (almost all directional).

Under which area of Artificial Intelligence is my knowledge store?

I’ve a maturing idea regarding a knowledge store.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Would a model like this translate well to a document or graph database?

I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships:

Would a model like this translate well to a document or graph database?

I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships:

Would a model like this translate well to a document or graph database?

I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships: