Is your feature request related to a problem? Please describe.
I'm frustrated by the lack of support for time-based sequencing in knowledge graphs. When working with data like movies, lifelogs, or event logs, it’s crucial to track events as they occur in sequence, building a "memory" of what happened and when. Without a built-in way to query events by order or specific time ranges, I can’t fully leverage knowledge graphs for analyzing the flow of events over time.
Describe the solution you'd like
I’d like knowledge graphs to support a time-based dimension that allows me to:
Query events or nodes by specific timestamps or time ranges.
Retrieve events in the order they happened, enabling queries like "What happened before/after this event?" or "Which events took place in this timeframe?"
Describe alternatives you’ve considered
One alternative would be to use a separate time-series database to manage timestamps, but this would add complexity and make it harder to analyze event relationships within the graph structure. Another option would be manually sorting events by timestamp in post-processing, but this quickly becomes inefficient as data scales.
Additional context
This feature would be invaluable for applications such as:
Movies: Querying scenes or dialogue in a timeline, e.g., "What scene followed this action?"
Lifelogs: Analyzing personal routines or events by day or week.
Event Logs: Investigating patterns in sequential events, useful for troubleshooting or timeline analysis.
Is your feature request related to a problem? Please describe.
I'm frustrated by the lack of support for time-based sequencing in knowledge graphs. When working with data like movies, lifelogs, or event logs, it’s crucial to track events as they occur in sequence, building a "memory" of what happened and when. Without a built-in way to query events by order or specific time ranges, I can’t fully leverage knowledge graphs for analyzing the flow of events over time.
Describe the solution you'd like
I’d like knowledge graphs to support a time-based dimension that allows me to:
Describe alternatives you’ve considered
One alternative would be to use a separate time-series database to manage timestamps, but this would add complexity and make it harder to analyze event relationships within the graph structure. Another option would be manually sorting events by timestamp in post-processing, but this quickly becomes inefficient as data scales.
Additional context
This feature would be invaluable for applications such as: