Project Info
Inspiration
One of our project partners came up with this idea during the summer. We decided that the hackathon is a great opportunity for us to bring the project to life.
What it does
What our article analysis does is that it analyzes and provides a summary of the article that the person entered. It summarizes the article by giving five key bullet points that are important to help with the user's understanding of the article. The program is also able to detect misinterpretation through semantic analysis.
How we built it
We used Hume.ai to be able to analyze semantic in text. We also used Together.ai for our LLM. We coded the project in python and Taipy is used in the backend.
Challenges we ran into
The challenges we ran into were being able to implement Hume.ai to be able to analyze the article that we entered and being able to create the LLM.
Accomplishments we're proud of
We were proud of the fact that we were able to fully implement the Hume.ai to work with the articles, as this took us the longest time to figure out.
What we learned
We learned that API are very helpful in creating our programs.
What's next
The next step is to be able to type in a concept and multiple articles popup with analysis and summaries.
Analysis
View
Metric
- 11
- 7
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- PythonIn code
2 of 2 appear in the indexed code.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
12 KB
Source files
9
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
NickCoding22/article_analysis
31 files · 50 KB · @ 223299a
Structure
Interface
1 file · 3%Screens, components and styles rendered to the user.
Application logic
16 files · 52%Domain rules, services and shared utilities.
Background jobs
9 files · 29%Work run outside a request: tasks, workers and schedules.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- Python99%
- CSS1%
- Markdown0%
Share of indexed source by file size. Binary and vendored files are excluded.
Feature verification
Article summarization via LLMVerified
Analyzes and provides a summary of the article the user entered
Claimed on Devposthigh confidenceBackend/Backend.py:7— analyze_website_LLM parses the article and sends it to together.Complete.create with a summarization prompt, returning the LLM output as 'main points'Backend/index.py:48— main3 calls Backend.analyze_website_LLM(str)['main points'] and wires it into the Taipy build_url task/output
Hume.ai integration for text semantic analysisVerified
We used Hume.ai to be able to analyze semantic in text
Claimed on Devposthigh confidenceBackend/SentimentAnalysis.py:12— imports HumeStreamClient and LanguageConfig from hume, connects with an API key, and sends article text via socket.send_text
Python implementationVerified
We coded the project in python
Claimed on Devposthigh confidenceBackend/Main.py— all backend logic (Main.py, Backend.py, Parser.py, SentimentAnalysis.py, index.py) is written in Python
Taipy backend/GUIVerified
Taipy is used in the backend
Claimed on Devposthigh confidenceBackend/index.py:1— imports taipy, configures Core scenario/tasks/data nodes, and defines a Taipy Gui page with input/submit/text controls wired to the analysis functions
Together.ai LLM integrationVerified
We also used Together.ai for our LLM
Claimed on Devposthigh confidenceBackend/Backend.py:2— imports together, sets together.api_key, and calls together.Complete.create with model togethercomputer/llama-2-7b-chat
User enters an article (URL) for analysisVerified
Analyzes the article that the person entered
Claimed on readmehigh confidenceBackend/index.py:101— GUI exposes an <|{input_topic}|input|> field and submit button feeding into the scenario that runs sentiment and summary tasks on the given URLBackend/Parser.py:12— parse_website(website_url) fetches and extracts paragraph text from the entered URL via requests/BeautifulSoup
Bias/misinterpretation detection via semantic sentiment analysisCode-supported
The program is able to detect misinterpretation through semantic analysis / determines bias in language
Claimed on Devpostmedium confidenceBackend/SentimentAnalysis.py:16— get_sentiment_from_article uses Hume's LanguageConfig(sentiment={}) to score article text into 9 sentiment bucketsBackend/Main.py:9— main() aggregates sentiment totals into a positive/negative/neutral label, but this measures sentiment/tone, not bias or 'misinterpretation' specifically; no distinct bias-detection logic exists
Five key bullet points summaryCode-supported
Summarizes the article by giving five key bullet points
Claimed on Devpostlow confidenceBackend/Backend.py:14— Prompt asks the LLM to 'summarize the following article in 5 sentence paragraph', not five bullet points; the output is a single text blob from the LLM, not a bulleted list, so the '5 bullet points' framing is only loosely implemented
Type a concept and multiple related articles pop up with analysis (future work)Code-supported
Next step is to be able to type in a concept and multiple articles popup with analysis and summaries
Claimed on Devpostlow confidenceBackend/GoogleSearcher.py:9— get_google_results(topic, amount) performs a Google search for a topic and returns multiple URLs, a plausible building block for this stated future feature, but it is not called from Main.py, Backend.py, or index.py, so it is not wired into the app
An AI agent derived these features from the project’s Devpost page and readme, then searched the code for each one. Verified features are backed by cited code; claimed-only features had no supporting code, which is not by itself proof a feature is missing.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.