WeSearch

LLM-Based Hierarchical Topic Modeling Tool

·7 min read · 0 reactions · 0 comments · 33 views
LLM-Based Hierarchical Topic Modeling Tool
TL;DR · WeSearch summary

The LLM-Based Hierarchical Topic Modeling Tool normalizes raw string values in JSONL files into reusable hierarchical categories using plain-language instructions. It requires Python, an API key for a LiteLLM-supported model, and a Rust compiler for installation, with optional Conda environment support. Users configure model keys in config.py or a .env file before running the provided scripts to transform the data.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 3,300 of its stories.

Original article
GitHub
Read full at GitHub →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGitHub
Canonical URLhttps://github.com/Tryhard-cs/LLM-Hierarchical-Topic-Modeling
Publication timeTue, 21 Jul 2026 16:26:11 +0000
Retrieval time2026-07-21T17:16:05.534Z
Last seen2026-07-21T17:16:05.534Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterG48g5Vsx31fQ
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Instruction-Driven Hierarchical Topic Normalizer Hierarchical topic modeling groups related labels into a taxonomy: broad topics at the top and increasingly specific subtopics below them. This tool is a practical, LLM-assisted version for JSONL data: it turns inconsistent raw strings into a reusable hierarchy that you steer with plain-language instructions. For example, it can map bad, neg, and negative to negative, or map search to Features|Search. It is designed for extracted Reddit-study data, but works with any JSONL file containing strings, nested objects, and arrays of objects. The input is a JSONL file with raw string values. The output is another JSONL file with the same records and structure, except that mapped values have been replaced by their normalized category paths.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub