Practical overview
When it fits
Use it as a reference implementation when you need to study or adapt a case-data workflow that pairs embedding-based retrieval with graph exploration.
Who it is for
- Developers prototyping legal-document retrieval that combines semantic search and graph relationships.
- Researchers exploring Supreme Court case data through processed embeddings and linked knowledge.
Documented uses
- Fetch and process raw Supreme Court case data.
- Generate embeddings for SCOTUS cases.
- Explore processed cases using vector search alongside a knowledge graph.
Requirements & limits
The repository is public and specifies an Apache-2.0 license. Running the documented workflow requires configuration for Neo4j, MongoDB, Pinecone and an OpenAI API key.
- Case processing and embedding generation are separate from starting the explorer; data processing must be completed first.
- Setup uses Poetry for Python dependencies and pnpm for Node.js dependencies.
- The processing notebooks are SCOTUS-focused; another corpus may need ingestion and metadata changes (Likely compatible).
- Using an embedding provider other than OpenAI requires modification; alternative-provider support is not demonstrated (Requires modification).
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the repository and prepare its case data
Install the documented Python and explorer dependencies, configure service credentials, and process Supreme Court cases for the application.
Before you start
- A MongoDB database, Neo4j account and Pinecone account
- An OpenAI API key
- Python dependencies managed with Poetry and Node.js dependencies managed with pnpm
Steps
Clone the repository.
From the repository root, run
poetry install.Enter the
explorerdirectory and runpnpm install.Create a
.envfile with the documented Neo4j, MongoDB, Pinecone and OpenAI settings.Use
process_raw.ipynbto fetch and process raw case data, thenprocess_scotus.ipynbto process SCOTUS cases and generate embeddings.
Expected outcome
The documented dependencies and service settings are in place, and the notebooks provide the case-processing and embedding stages used before starting the explorer.
Guide limitations
- The setup instructions require accounts or database access for the named services.
- The application start command is documented only after data processing is complete.
Start the explorer after processing case data
Start the application from its explorer directory once case processing is complete.
Before you start
- The repository dependencies installed and environment variables configured
- Case data processed using the documented notebooks
Steps
Change to the
explorerdirectory.Run
pnpm dev.
Expected outcome
The documented development command starts the application after its data-processing stage.
Guide limitations
- The README does not provide further run-time or deployment instructions.
Compare options for Vector search
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Pinecone – Neo4j integration demo | Fetch and process raw Supreme Court case data. | Cloud, Web | The repository is public and specifies an Apache-2.0 license. Running the documented workflow requires configuration for Neo4j, MongoDB, Pinecone and an OpenAI API key. |
| Chatbot with PDF for Semantic Search | Prepare document content as embeddings and save it to a supported vector database. | Web | The repository is identified as open source and publicly visible on GitHub. |
| AI LLM Playground | Ask questions about PDF documents through an assistant interface. | Web |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- pinecone-io/pinecone-neo4j-explorer · Official homepage title · retained in its source language

