(2/2) Applying our reified ‘interpretive act’ to such deep chains — without Barabucci’s ‘collapse to reality’ — would be a fascinating stress test for our graph’s performance. I think we should work through this case by developing a dedicated ‘Provenance Module’ within IDEA.

(1/2) Thank you for the pointer, Camilla. Barabucci et al. certainly put their finger on the 'data sins' we are trying to address.
While IDEA currently focuses on the structural analysis of visual content, their Colosseum example highlights the vital complexity of provenance and object biographies.

Thank you. The cold start is a sobering reminder of the task's scale. v0.9.2 is just a modest first step. We released it early precisely because we need the community's scrutiny to find the flaws in our logic. There is still so much to learn.

Neo4j for the epistemic/query layer.

However, Postgres will be our Single Source of Truth. We love strict relational integrity for data management.

We treat the graph as a projection. Writing recursive CTEs is technically possible in SQL, but Cypher is just kinder to my sanity.

Polishing the graph model before release.

Current struggle: Relations. RDF suggests "Hero -holding-> Sword". But our ontology demands Reification: "Hero -REL-> Holding -OBJ-> Sword" to properly model the act itself.

Praying I won't regret the extra hop cost later. 🤞

3/3 #GraphDB #Neo4j

Currently pivoting 50k legacy records from SQL to Graph using AI. Why? Because recursive self-joins to simulate ontology traversals only look good on paper. In production, they hurt.

2/3 #RSEng #Numismatics #DigitalHumanities