← All speakers

Bio, Work & Ideas

Andreas Kollegger

Conference affiliation: Neo4j · 2026

Andreas Kollegger is Director of Applied AI Research at Neo4j, developing graph-based approaches that help AI systems understand organizational context, assess risk, and make accountable decisions. His career spans NASA science missions, healthcare informatics in Zambia, and more than a decade building and explaining graph technology.

Kollegger encountered graph databases while developing medical informatics systems in Zambia, then joined Neo4j’s early core-engineering organization. He contributed to the Neo4j 1.3 manual and moved into product experience design by 2013. Subsequent responsibilities included developer advocacy and generative AI leadership before his transition into applied AI research. His early work on making relationships between records useful now informs his approach to retrieval, organizational memory, and autonomous decision-making.

  • Build knowledge graphs around real questions. Start with generic entity labels, simple relationship types, and representative data; evaluate whether the system answers its intended questions before refining the schema or expanding coverage.
  • Make relationships part of retrieval. Connecting document chunks exposes information unavailable from isolated passages, including relationships and graph communities. His approach to graph-enhanced retrieval distinguishes a vector index from a complete search system: graph properties, traversal, and post-filtering determine which results are appropriate.
  • Give agents explicit decision boundaries. His framework for decision-aware AI agents considers objectives, prior decisions, organizational rules, risk, reversibility, and the cost of mistakes. Specialized agents can propose alternatives while separate agents assess their authority to act, escalate uncertain decisions, and preserve reasoning traces and decision precedents.

Kollegger’s agentic knowledge-graph workshop demonstrates multi-agent knowledge-graph construction. His aie-matrix project explores a virtual conference populated by autonomous personal agents. Both develop his central concern: giving AI systems enough connected knowledge, policy, memory, and authority to act responsibly.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Graphs can give agents relevant knowledge, but decisions also need policies, risk assessment, authority checks, and a record that future agents can consult.

  • Give the agent the knowledge it is missing
    0:38 ↗
  • Context graphs add the why
    2:55 ↗
  • Retrieve the relevant graph context
    5:56 ↗
  • Restock the fridge—or preserve the rent money?
    6:57 ↗
  • Frame the immediate decision
    9:24 ↗
  • Balance precedent with current rules
    10:42 ↗
  • Assess risk before optimizing value
    11:32 ↗
  • Separate proposals from authorized action
    13:47 ↗
  • Turn the outcome into future precedent
    14:51 ↗
  • Implement the workflow for a specific domain
    15:29 ↗

Key ideas

Scroll to read ↓

A graph can connect retrieved chunks to their sources, conversations and neighbors, giving engineers practical ways to diagnose redundancy, diversify context and trace what their applications amplify.

  • What information is your retriever missing?
    5:12 ↗
  • Put application activity in the graph
    13:49 ↗
  • Explore more relationships, then load the workshop environment
    21:57 ↗
  • Follow Agent Neo’s conversations into their context
    31:36 ↗
  • Store searchable representations and scope retrieval
    37:43 ↗
  • Restore the snapshot and inspect the graph
    47:01 ↗
  • Connect, cluster, curate
    56:54 ↗
  • Project only the data the algorithm needs
    1:03:41 ↗
  • A tight cluster can reveal a bad corpus
    1:08:04 ↗
  • Consolidate repeated content while keeping its sources
    1:14:52 ↗
  • Trace where conversations go and what they amplify
    1:18:13 ↗
  • Choose where algorithm results live
    1:22:59 ↗
  • Make traceability part of building the system
    1:27:28 ↗
  • Carry context across agent handoffs
    1:32:05 ↗
  • What communities actually change in retrieval
    1:36:13 ↗

References