# True Knowledge Graph Capabilities

**URL:** <https://community.palantir.com/t/true-knowledge-graph-capabilities/1045>\
**Category:** Product Feedback\
**Tags:** vertex, summer-2024-planning\
**Created:** [August 15, 2024, 6:43pm UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045 "2024-08-15T18:43:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![a27420e6cc562fe21ae1](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/a27420e6cc562fe21ae1/32/687_2.png) [@a27420e6cc562fe21ae1](https://community.palantir.com/u/a27420e6cc562fe21ae1)\
**Post date:** [August 15, 2024, 6:43pm UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/1 "2024-08-15T18:43:07Z")

</div>

Ability to have a true Neo4j-like Knowledge graph capabilities within Foundry ecosystem.

Knowledge Graph elements being:

```
  Nodes (Entities):
        Represent real-world objects, concepts, or ideas
        Examples: people, places, organizations, events, products

  Edges (Relationships):
        Connect nodes to show how they are related
        Describe the nature of the connection between entities
        Examples: "works for," "located in," "is a type of"

  Properties (Attributes):
        Additional information associated with nodes or edges
        Provide more details about entities or relationships
        Examples: name, date of birth, job title, timestamp

```

# Background for the request

Having experimented a lot with Traditional RAG vs Knowledge Graph RAG outside of Foundry, we are finding using Knowledge Graphs helpful in many scenarios that we want to use within Foundry. So we decided to have a go at what we could do within Foundry to emulate a Knowledge Graph using the Ontology, and Vertex.

The first challenge was how we could incorporate the main characteristics of a Knowledge Graph inside Foundry.  
The approach we took was to create two Ontology Objects, Entity and Relationship.

- Entity had the Node details and associated properties
- Relationship has the Edge details and appropriate properties, with a link ‘from’ one entity, and a link ‘to’ another entity

We then used an LLM to parse multiple PDFs with the prompt defining the Entity values we want (ie Study, Therapeutic Area, Indication etc) and the relevant properties we want on it, and likewise for the Relationship.  
From the parsed LLM response we went on to create records in the two Ontology objects, with appropriate linkage etc.  
With embeddings etc as well we could do simple semantic searching and search arounds between the Node object (both the one as the ‘from’ and the one as the ‘to’ and the Relationship object that bridges them.  
We went on to have a little Workshop app that allowed a side-by-side comparison of Traditional RAG and Knowledge Graph RAG results.

On from that, we wanted to use Vertex to represent it. Mixed results on this because it ultimately shows both the Entities and the Relationship objects as nodes. With styling we could set the Relationship node to be invisibly small and so only the Relationship Text remains, which made it look more ‘Knowledge Graph’ like, but it felt very crude and needed a lot of manual aligning to make it look good.

So, yes, adding Knowledge Graph capabilities, or moving towards that, would be extremely welcome.

---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [November 27, 2024, 11:50am UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/2 "2024-11-27T11:50:08Z")

</div>



---

<div class="post-metadata">

**Author:** ![f297f0084b395efb59ba](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/f297f0084b395efb59ba/32/1461_2.png) [@f297f0084b395efb59ba](https://community.palantir.com/u/f297f0084b395efb59ba)\
**Post date:** [November 29, 2024, 11:18am UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/3 "2024-11-29T11:18:41Z")

</div>

Vote yes for this request. We’re getting more interests to have this capability in Foundry.

---

<div class="post-metadata">

**Author:** ![Flackermann](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/flackermann/32/612_2.png) [@Flackermann](https://community.palantir.com/u/Flackermann)\
**Post date:** [December 9, 2024, 10:30am UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/4 "2024-12-09T10:30:45Z")

</div>

Did you know, that you can configure the relationship object in the ontology manager to appear as an edge in vertex?  
[Vertex • Configuration • Configure link merging • Palantir](https://www.palantir.com/docs/foundry/vertex/link-merging/)

Also, you could do the searcharound and graph building using functions on objects so that you also have the right lables on the edges accordingly:

[Vertex • Graphs • Generate graphs using Functions • Palantir](https://www.palantir.com/docs/foundry/vertex/generate-graph-functions/)

It seems that with your logic / ontology, this could be a rather generic implementation.

---

<div class="post-metadata">

**Author:** ![a27420e6cc562fe21ae1](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/a27420e6cc562fe21ae1/32/687_2.png) [@a27420e6cc562fe21ae1](https://community.palantir.com/u/a27420e6cc562fe21ae1)\
**Post date:** [December 10, 2024, 1:13pm UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/5 "2024-12-10T13:13:20Z")

</div>

Hi @Flackermann , thanks for the message. Yes I tried something similar and it kind of does the job but feels very cumbersome and not a real KG.

---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [March 30, 2025, 2:48am UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/6 "2025-03-30T02:48:31Z")

</div>



---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [July 16, 2025, 4:11pm UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/7 "2025-07-16T16:11:17Z")

</div>



---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [December 16, 2025, 11:11am UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/8 "2025-12-16T11:11:54Z")

</div>



---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\
**Post date:** [July 20, 2026, 3:03pm UTC](https://community.palantir.com/t/true-knowledge-graph-capabilities/1045/9 "2026-07-20T15:03:46Z")

</div>


