1Copy the prompt text below by clicking the copy button.
2Open your preferred AI tool (Claude, or any compatible model).
3Paste the prompt and customize any bracketed placeholders to match your needs.
4Generate and iterate — adjust details for the perfect result.
Best for
✓Senior engineers using AI for the boring parts of the workflow
✓Developers shipping ai coding on a tight deadline
✓Tech leads enforcing patterns across a team
✓Solo founders shipping side projects fast
Works with
Optimised for Claude for ai coding. Compatible with the models below — adjust syntax if you switch platforms.
Claude (Sonnet/Opus)ChatGPT (GPT-4.1)GeminiCursorAider
Frequently asked questions
What is the "Organizational Knowledge Graph Builder" prompt and what does it produce?
Organizational Knowledge Graph Builder is a ai coding prompt published on TainerAI. OntologyRAG ✅ Maps entities and relationships from raw org content (emails, docs, notes, SharePoint)
✅ Outputs structured ontology: People → Roles → Processes → Systems → Policies → Decisions
✅ Designed to feed directly… Tagged: Code, JavaScript, Python.
Which AI model works best for the "Organizational Knowledge Graph Builder" prompt?
This prompt is tuned for Claude, but the structure ports cleanly to Claude (Sonnet/Opus), ChatGPT (GPT-4.1), Gemini, Cursor with minor adjustments. Keep the same input variables; only change the system message format if the target model expects a different schema.
How do I customise this prompt for my ai coding?
Copy the prompt content, replace any variables in [brackets] with your specifics (relevant areas to customise: Code, JavaScript, Python), and run it through Claude. If the first generation misses, change one variable at a time — that isolates which part of the prompt needs adjustment instead of triggering full re-rolls.
Can I use the output of this prompt in commercial work?
Yes. Every TainerAI free prompt — including this one — comes with a commercial-use license under your TainerAI account. You can ship the output in client work, paid products, courses, or your own SaaS. The only restriction is that you may not resell the unmodified prompt itself as a standalone listing on another marketplace.
Prompt Content
Prompt Details
Model
(claude-4-6-sonnet)
Token size
1,694
Example input
[RAW_CONTENT]: Notes from Slack and Notion: - Sarah (Head of Ops) manages onboarding process for new clients - Onboarding is done through HubSpot and internal Notion templates - All onboarding must follow the Client Experience Policy v2 - If onboarding is completed, it triggers the Customer Success Handoff process - John uses HubSpot daily to track deals and onboarding progress - Decision: On Jan 5, CEO approved switching from Trello to Notion for internal workflows
[EXISTING_ONTOLOGY]: NONE
[OUTPUT_FORMAT]: markdown tables
Example output
Running the extraction now.
---
ONTOLOGY METADATA:
- **source:** Slack and Notion notes
- **date_processed:** April 14, 2026
- **entity_count:** 11
- **relationship_count:** 9
- **gaps_detected:** 2 critical, 1 moderate, 1 low
- **confidence_overall:** MODERATE
---
## ENTITIES
### PERSONS
| Name | Role | Department | Confidence | Aliases |
|------|------|------------|------------|---------|
| Sarah | Head of Ops | Operations (implied) | HIGH | — |
| John | Unspecified | Unknown | MODERATE | — |
| CEO | Chief Executive Officer | Executive | MODERATE | — |
### PROCESSES
| Process Name | Owner | System | Governing Policy | Confidence |
|---|---|---|---|---|
| Client Onboarding | Sarah | HubSpot, Notion | Client Experience Policy v2 | HIGH |
| Customer Success Handoff | UNOWNED | UNKNOWN | UNGOVERNED | MODERATE |
### SYSTEMS
| System Name | Used By | Processes Running | Confidence |
|---|---|---|---|
| HubSpot | John, Sarah (implied) | Client Onboarding, Deal Tracking | HIGH |
| Notion | Sarah (implied) | Client Onboarding, Internal Workflows | HIGH |
| Trello | UNKNOWN | Internal Workflows (deprecated) | MODERATE |
### POLICIES
| Policy Name | Governs | Enforced By | Confidence |
|---|---|---|---|
| Client Experience Policy v2 | Client Onboarding | UNKNOWN (no enforcer stated) | HIGH |
### DECISIONS
| Decision | Made By | Date | Affects | Confidence |
|---|---|---|---|---|
| Switch from Trello to Notion for internal workflows | CEO | Jan 5 | Internal workflow processes | HIGH |
### CONCEPTS (Glossary)
| Term | Definition (from source) | Related Process/System |
|---|---|---|
| Customer Success Handoff | Process triggered upon onboarding completion; transfers client to success team | Client Onboarding |
| Client Experience Policy v2 | Governance standard that all onboarding activities must comply with | Client Onboarding |
---
## RELATIONSHIPS (Graph Triples)
| Subject | Relationship | Object | Confidence | Source |
|---|---|---|---|---|
| Sarah | OWNS | Client Onboarding | HIGH | "Sarah (Head of Ops) manages onboarding process for new clients" |
| Client Onboarding | RUNS_ON | HubSpot | HIGH | "Onboarding is done through HubSpot and internal Notion templates" |
| Client Onboarding | RUNS_ON | Notion | HIGH | "Onboarding is done through HubSpot and internal Notion templates" |
| Client Onboarding | GOVERNED_BY | Client Experience Policy v2 | HIGH | "All onboarding must follow the Client Experience Policy v2" |
| Client Onboarding | TRIGGERS | Customer Success Handoff | HIGH | "If onboarding is completed, it triggers the Customer Success Handoff process" |
| John | USES | HubSpot | HIGH | "John uses HubSpot daily to track deals and onboarding progress" |
| CEO | DECISION → AFFECTS | Notion (replaces Trello) | HIGH | "On Jan 5, CEO approved switching from Trello to Notion for internal workflows" |
| Decision (Trello→Notion) | AFFECTS | Internal Workflows (PROCESS implied) | MODERATE | "switching from Trello to Notion for internal workflows" |
| Client Experience Policy v2 | APPLIES_TO | Client Onboarding | HIGH | "All onboarding must follow the Client Experience Policy v2" |
---
## GAPS REPORT
**CRITICAL:**
- **Customer Success Handoff has no owner (PERSON → OWNS)** — No individual is identified as responsible for this process. Recommended action: identify and assign a process owner (likely someone on the Customer Success team).
- **Customer Success Handoff has no governing policy** — The process is triggered by onboarding but operates ungoverned. Recommended action: confirm whether Client Experience Policy v2 extends to it, or document a separate policy.
**MODERATE:**
- **Client Experience Policy v2 has no named enforcer** — The policy exists and governs onboarding, but no person is assigned to enforce or maintain it. Recommended action: assign ownership to Sarah or a compliance role.
**LOW:**
- **John's role and department are unspecified** — He is a HubSpot user with deal/onboarding visibility but his title and team are not stated. Recommended action: clarify role in source documentation.
---
## INGESTION READINESS
| Metric | Value |
|---|---|
| Entities extracted | 11 |
| Relationships mapped | 9 |
| Graph triples ready | 9 |
| Critical gaps | 2 |
| Moderate gaps | 1 |
| Low gaps | 1 |
| Output format | Markdown tables |
| **Ready for indexing** | **YES WITH WARNINGS** |
> ⚠️ Resolve critical gaps (Customer Success Handoff ownership + governance) before treating this ontology as complete for RAG traversal. Traversal queries involving post-onboarding workflows will dead-end without an owner node on that process.
Open in your AI tool
Copies the prompt, then opens the app
Comments
Sign in to join the conversation.
No comments yet. Be the first to share your thoughts.
Sign in to comment
Join the conversation — takes 10 seconds with Google.
Comments
Sign in to join the conversation.