neo4j
.
neo4j://
, neo4j+s://
, bolt://
, or bolt+s://
; followed by localhost
or the host name; and sometimes ending with a colon and the port number (such as :7687
). For example:
neo4j+s://<host-name>
. A port number is not used or needed.bolt://localhost:7687
neo4j
for user data and another
named system
for system data and metadata. Some Neo4j deployment types support more than these two databases per deployment;
Neo4j Aura instances do not.
NEO4J_USERNAME
- The name of the target user with access to the target Neo4j deployment, represented by --username
(CLI) or username
(Python).NEO4J_PASSWORD
- The user’s password, represented by --password
(CLI) or password
(Python).NEO4J_URI
- The connection URI for the deployment, represented by --uri
(CLI) or uri
(Python).NEO4J_DATABASE
- The name of the database in the deployment, represented by --database
(CLI) or database
(Python).--partition-by-api
option (CLI) or partition_by_api
(Python) parameter to specify where files are processed:
--partition-by-api
(CLI) or partition_by_api
(Python), or explicitly specify partition_by_api=False
(Python).
Local file processing does not use an Unstructured API key or API URL, so you can also omit the following, if they appear:
--api-key $UNSTRUCTURED_API_KEY
(CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY")
(Python)--partition-endpoint $UNSTRUCTURED_API_URL
(CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL")
(Python)UNSTRUCTURED_API_KEY
and UNSTRUCTURED_API_URL
--partition-by-api
(CLI) or partition_by_api=True
(Python).
Unstructured also requires an Unstructured API key and API URL, by adding the following:
--api-key $UNSTRUCTURED_API_KEY
(CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY")
(Python)--partition-endpoint $UNSTRUCTURED_API_URL
(CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL")
(Python)UNSTRUCTURED_API_KEY
and UNSTRUCTURED_API_URL
, representing your API key and API URL, respectively.https://api.unstructuredapp.io/general/v0/general
, which is the API URL for the Unstructured Partition Endpoint. However, you should always use the URL that was provided to you when your Unstructured account was created. If you do not have this URL, contact Unstructured Sales at sales@unstructured.io.If you do not have an API key, get one now.If the Unstructured API is self-hosted, the process
for generating Unstructured API keys, and the Unstructured API URL that you use, are different.
For details, contact Unstructured Sales at
sales@unstructured.io.Document
node represents the source file.UnstructuredElement
nodes represent the source file’s Unstructured Element
objects, before chunking.Chunk
nodes represent the source file’s Unstructured Element
objects, after chunking.UnstructuredElement
node has a PART_OF_DOCUMENT
relationship with the Document
node.Chunk
node also has a PART_OF_DOCUMENT
relationship with the Document
node.UnstructuredElement
node has a PART_OF_CHUNK
relationship with a Chunk
element.Chunk
node, except for the “last” Chunk
node, has a NEXT_CHUNK
relationship with its “next” Chunk
node.Chunk
to Document
relationships:
UnstructuredElement
to Document
relationships:
UnstructuredElement
to Chunk
relationships:
Chunk
to Chunk
relationships:
UnstructuredElement
to Chunk
to Document
relationships:
UnstructuredElements
containing the text jury
, and show their Chunk
relationships:
Chunk
with the specified id
, and show its UnstructuredElement
relationships:
Entity
nodes in the graph.
This additional graph ouput of the Neo4j destination connector is represented in the following diagram:
In the preceding diagram:
Chunk
node represents one of the source file’s Unstructured Element
objects, after chunking.Entity
node represents a recognized entity.Chunk
node can have HAS_ENTITY
relationships with Entity
nodes.Entity
node can have ENTITY_TYPE
relationships with other Entity
nodes.Entity
to Entity
relationships:
Entity
nodes containing the text PERSON
, and show their Entity
relationships:
Entity
nodes containing the text amendment
, and show their Chunk
relationships:
Entity
nodes containing the text PERSON
, and show their Entity
to Entity
to Chunk
relationships: