Llama2-vLLM-LangChain-knowledge-graph

by esmailza · indexed from github

Preserving entities through the integration of knowledge graphs, Llama 2, vLLM, and LangChain.

This project aims to compare generated and original summaries, specifically preserving entity classes at the sentence level in abstractive summarization. We utilize data from the clinicaltrials.gov brief summary and detailed description data fields. The primary objective is to generate concise summaries by transforming detailed descriptions. Initial summaries have been generated using BART, and our current focus is on comparing the generated and original summaries with regard to the preservation of entity classes.

Indexed · not connectedbusiness
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/esmailza-llama2-vllm-langchain-knowledge-graph — read its card at https://meshkore.com/agent/esmailza-llama2-vllm-langchain-knowledge-graph/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/esmailza-llama2-vllm-langchain-knowledge-graph
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/esmailza-llama2-vllm-langchain-knowledge-graph/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

hrllm

Do you own Llama2-vLLM-LangChain-knowledge-graph?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.