Loading...
Loading...
Compare original and translation side by side
/context-manager/nlp-engineer/database-administrator/technical-writer/context-manager/nlp-engineer/database-administrator/technical-writerKnowledge Structure Needed?
├── Hierarchical (taxonomy)
│ └── Tree structure, parent-child relationships
├── Graph (connected entities)
│ └── Nodes + edges, property graphs
├── Hybrid (RAG + Graph)
│ └── Vector embeddings + knowledge graph
└── Flat (simple retrieval)
└── Standard vector store sufficient是否需要知识结构化?
├── 层级式(分类法)
│ └── 树形结构、父子关系
├── 图结构(关联实体)
│ └── 节点 + 边、属性图
├── 混合式(RAG + 图)
│ └── 向量嵌入 + 知识图谱
└── 扁平化(简单检索)
└── 标准向量存储即可满足需求| Anti-Pattern | Problem | Correct Approach |
|---|---|---|
| No provenance tracking | Cannot verify claims | Track source for every fact |
| Over-complex ontology | Hard to maintain and query | Start simple, evolve as needed |
| Ignoring contradictions | Inconsistent knowledge base | Flag and resolve conflicts |
| Static schema | Breaks with new domains | Design for extensibility |
| Blind extraction trust | Hallucinated relationships | Validate with confidence thresholds |
| 反模式 | 问题 | 正确做法 |
|---|---|---|
| 不跟踪来源 | 无法验证主张 | 为每个事实跟踪来源 |
| 本体过于复杂 | 难以维护与查询 | 从简单开始,按需演进 |
| 忽略矛盾 | 知识库不一致 | 标记并解决冲突 |
| 静态架构 | 新增领域时失效 | 为可扩展性而设计 |
| 盲目信任提取结果 | 生成幻觉关系 | 结合置信度阈值进行验证 |