9148c358d0
Topic_Agent/Topic_Blog/Topics/Topics_Biz/Topics_Meeting/Topics_Rag의 마크다운 지식 문서를 Topic_General/Topic_Programming/Topic_Graphic/Topic_Business 4개 카테고리로 재분류. - 중복 제거: frontmatter의 status:duplicate/merged + duplicate_of/redirect_to 필드로 자기 자신을 중복으로 선언한 리다이렉트 stub 1032개 제거, 완전 동일 내용 파일 472개 제거, 동일 파일명·다른 내용 충돌 시 더 큰(완전한) 버전만 유지(162개 제거) — 총 1639개 중복 제거. - 분류: 폴더 단위로 명확한 항목(AI_and_ML/Coding/Architecture 등 → Programming, Comfyui/Visual_Effects → Graphic, Topics_Biz/Topics_Meeting/사업 등 → Business, Poetic_Blog_Writing/창의성/Game_Design 등 → General)은 폴더 우선순위로, 나머지 혼재 폴더(Topic_Agent/Topic_Blog/Topics 루트/Thinking & Reasoning/Other/UI_UX_Assets)는 title/tags 키워드 스코어링으로 파일 단위 분류(불명확한 경우 General로 폴백). 원본 폴더명은 "From_*" 서브폴더로 보존해 추적 가능성 유지. - 최종 배치: Programming 2784 / General 1608 / Graphic 285 / Business 249 = 4926개 문서. - 에이전트 운영 상태(.astra/.agent/.obsidian/sessions/memory/_company/docs/lessons/_shared/src)는 지식 콘텐츠가 아니므로 재분류 대상에서 제외하고 원위치 유지. - Topics/Topic_email(상위 보호 폴더 Topic_email과 파일명 100% 중복) 삭제 — 보호 폴더 자체는 미변경. - 완전히 비게 된 Topic_Agent/Topic_Blog/Topics_Biz/Topics_Rag 폴더 제거.
5.4 KiB
5.4 KiB
id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack
| id | title | category | status | canonical_id | aliases | duplicate_of | source_trust_level | confidence_score | verification_status | tags | raw_sources | last_reinforced | github_commit | tech_stack | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| wiki-2026-0508-text-mining | Text Mining | 10_Wiki/Topics | verified | self |
|
none | A | 0.9 | applied |
|
2026-05-10 | pending |
|
Text Mining
매 한 줄
"매 unstructured text → structured signal". Text mining 매 large text corpora 에서 patterns / entities / relationships / sentiment 의 extract 하는 분야. 매 traditional (TF-IDF, NER models) 에서 매 LLM-based extraction (structured output, function calling) 으로 매 paradigm shift.
매 핵심
매 traditional pipeline
- Tokenization → POS tagging → NER → dependency parsing → sentiment → topic modeling.
- Tools: spaCy, NLTK, scikit-learn (TF-IDF + classifiers), gensim (LDA).
- 매 production NER: spaCy
transformerspipeline or fine-tuned BERT.
매 modern (LLM-based)
- Structured output — 매 LLM 이 JSON schema 의 fill (Claude tool use, OpenAI structured output, Outlines).
- Few-shot extraction — 매 fine-tune 없이 매 5 examples 만으로 task 의 정의.
- Long-context — 매 200k+ token document 의 single-shot processing.
- 매 cost trade-off: spaCy NER ~$0.0001/doc vs LLM ~$0.01/doc — 매 batch + small model (Haiku, gpt-4o-mini) 으로 reduce.
매 응용
- Resume parsing, contract analysis (entity + clause extraction).
- Customer feedback aggregation (sentiment + topic).
- Biomedical literature mining (gene/protein/disease NER).
💻 패턴
spaCy NER (traditional)
import spacy
nlp = spacy.load("en_core_web_trf")
doc = nlp("Apple acquired Anthropic for $50B in March 2025.")
for ent in doc.ents:
print(ent.text, ent.label_)
# Apple ORG, Anthropic ORG, $50B MONEY, March 2025 DATE
TF-IDF + classifier
from sklearn.feature_extraction.text import TfidfVectorizer
from sklearn.linear_model import LogisticRegression
from sklearn.pipeline import Pipeline
pipe = Pipeline([
("tfidf", TfidfVectorizer(ngram_range=(1, 2), max_features=20000)),
("clf", LogisticRegression(max_iter=1000)),
])
pipe.fit(X_train, y_train)
LLM structured extraction (Claude)
from anthropic import Anthropic
from pydantic import BaseModel
class Contract(BaseModel):
parties: list[str]
effective_date: str
total_value_usd: float | None
governing_law: str | None
client = Anthropic()
resp = client.messages.create(
model="claude-opus-4-7",
max_tokens=2000,
tools=[{
"name": "extract_contract",
"input_schema": Contract.model_json_schema(),
}],
tool_choice={"type": "tool", "name": "extract_contract"},
messages=[{"role": "user", "content": contract_text}],
)
data = Contract(**resp.content[0].input)
Topic modeling (BERTopic)
from bertopic import BERTopic
from sentence_transformers import SentenceTransformer
embed = SentenceTransformer("BAAI/bge-large-en-v1.5")
topic_model = BERTopic(embedding_model=embed, min_topic_size=10)
topics, probs = topic_model.fit_transform(docs)
topic_model.get_topic_info()
Long-context document QA
# 200k token contract → single LLM call
resp = client.messages.create(
model="claude-opus-4-7",
max_tokens=4000,
messages=[{"role": "user", "content": [
{"type": "text", "text": contract_full_text,
"cache_control": {"type": "ephemeral"}},
{"type": "text", "text": "Extract all change-of-control provisions."},
]}],
)
Hybrid (LLM + regex precheck)
import re
DATE_RE = re.compile(r"\b\d{4}-\d{2}-\d{2}\b")
candidates = DATE_RE.findall(text)
# 매 LLM 의 candidate 만 disambiguate — 매 cost reduce
매 결정 기준
| 상황 | Approach |
|---|---|
| High-volume (M docs/day) NER | spaCy / fine-tuned BERT |
| Complex schema, low volume | LLM structured output |
| Topic discovery | BERTopic / embeddings + clustering |
| Sentiment | Fine-tuned RoBERTa or LLM |
| Long documents (>50k tokens) | LLM with caching |
| Domain-specific (legal, medical) | Fine-tune + LLM hybrid |
기본값: 매 prototype LLM, 매 production 은 LLM (low volume) or distilled fine-tuned model (high volume).
🔗 Graph
- 부모: Information Retrieval
- 변형: Named-Entity-Recognition · Sentiment-Analysis
- 응용: RAG · Search
- Adjacent: Embeddings
🤖 LLM 활용
언제: 매 unstructured text corpus 의 query / extract / classify, schema-driven extraction, low-to-medium volume. 언제 X: 매 milli-second latency 의 필요 (real-time chat moderation) — 매 small distilled model.
❌ 안티패턴
- Regex-only complex extraction: 매 brittle — 매 LLM hybrid 로 graceful.
- No evaluation set: 매 LLM 매 hallucinate — 매 ground-truth eval 의 maintain.
- Full-document LLM 의 every query: 매 cache or pre-extract structured DB.
- Unicode normalization 의 skip: 매 Korean/CJK text 매 NFC normalize 필수.
🧪 검증 / 중복
- Verified (spaCy 3.x docs, Anthropic structured output guide, BERTopic, 2024-2026 NLP practice).
- 신뢰도 A.
🕓 Changelog
| 날짜 | 변경 |
|---|---|
| 2026-05-08 | Phase 1 |
| 2026-05-10 | Manual cleanup — traditional + LLM-based extraction patterns |