> For the complete documentation index, see [llms.txt](https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/graph.build-studio/node-and-edge-settings.md).

# Node and Edge Settings

## Entity Settings

Double-click any entity to view its settings.

<figure><img src="/files/UcHv5PBqNpEwH8NWrxzG" alt=""><figcaption></figcaption></figure>

The main settings area contains fields for Identifier and Type/Class (Label is used instead of type for LPG), as well as a prefix section for each.\
For LPG, namespace prefixes are optional and only appear in the entity settings if namespaces are included in the setup step 2 . \
The Identifier field displays the data field from the source being pulled into the entity. For example, if the identifier is `{transaction_no}`, the curly braces indicate that the data is being templated. Text can be prepended or appended around the braces if needed.

<figure><img src="/files/c4QS4VjPmF60BtOaAcC0" alt=""><figcaption></figcaption></figure>

For instance, if the transaction number in the first record of the source data is 123456, using a prefix would return `123456-retail` (prefixes are optional for Labelled Property Graphs). The Type field assigns an RDF Class to the resource created by the entity (Semantic Graph) or adds a label to the node (LPG).

## Attribute Settings

Double-click any attribute to view its settings.

<figure><img src="/files/VNNwyuqZylLNLUtT0UAG" alt=""><figcaption></figcaption></figure>

The Template field shows the data being used for the attribute within curly braces. Again, text can be prepended or appended. The DataType field defines the XSD data type for the attribute. Additional options, such as setting a Language and a Named Graph, can be accessed in the Advanced Settings.

## Edge / Predicate Settings

Double-click any edge to view its settings.

<figure><img src="/files/XnH7NNogVTZekhmoXiWD" alt=""><figcaption></figcaption></figure>

For edges/predicates, all that is required is a Name and a Prefix.

## Floating Action Button

The Floating Action Button (FAB) is located in the bottom-right corner of the modelling area. It allows you to create Entities/Nodes, Blank Nodes, and Attributes/Properties without dragging and dropping fields from the input tab. This enables users to create models when they are uncertain about the fields they want to use or before the source data is available.

<figure><img src="/files/9pR5ZAZNJlcCELFsL88U" alt=""><figcaption></figcaption></figure>

After pressing the FAB, a list of different graph elements will appear. You can then select a type to use in your model. Upon selection, the element will appear in the modelling area with the settings pane open. These fields don’t need to be filled out immediately; they only become necessary when transforming data. However, mandatory fields must be completed before the model can be used for data conversion.

When you're ready to transform data for an entity/node, you'll need to manually enter the source data field name into the Identifier field. You'll also need to select the Source File from a dropdown and choose the appropriate Iterator, which determines how the data will be iterated over.

<figure><img src="/files/SrZP45VDl7VueM93tMoX" alt=""><figcaption></figcaption></figure>

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/graph.build-studio/node-and-edge-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.