Connect with us

Artificial Intelligence

AWS GraphRAG deployment cuts drug research cycles by 87% — here’s how

Published

on

How AWS GraphRAG deployment cuts drug research cycles by 87%

An AWS GraphRAG deployment has slashed pharmaceutical research and development cycles by 87 percent. The breakthrough came from stitching together proprietary databases that had long been isolated — clinical metrics, internal lab notes, engineering logs — into a single, queryable knowledge graph. What once took over six months per iteration now wraps up in three weeks.

Historically, the initial data-gathering and screening phases of drug discovery yielded a success rate of just five percent. Critical datasets lived in separate storage environments, effectively blocking data scientists from spotting hidden correlations. When senior researchers left, they took project context with them, stalling active work. AWS built a solution to connect these systems, combining graph databases with natural language processing.

The architecture behind the acceleration

The setup relies on a GraphRAG framework using Amazon Neptune Analytics and Amazon Bedrock to turn disconnected data points into a searchable network. Users submit standard natural language queries and receive answers mapped to verified domain literature and internal datasets.

But unifying isolated proprietary datasets with unstructured open-access repositories introduces significant data normalisation challenges. Strict schema governance is required to prevent inaccurate relational mapping and mitigate the risk of hallucinations — a well-known pitfall in retrieval-augmented generation systems.

Knowledge graph construction

Companies can plug in their own knowledge graphs. The system pulls in messy, unstructured files from public databases like PubMed and mixes them with internal corporate records. Tools like Amazon Comprehend Medical scan this text to extract standard medical codes. Amazon Bedrock, running Anthropic’s Claude 4.5 Sonnet, summarises document contents and determines topical relevance.

AWS Lambda functions and Amazon S3 bulk loads then route these processed elements into Amazon Neptune Analytics. The resulting knowledge graph structures data into discrete nodes representing core entities — domain-specific classes, authors, source journals, and embedded text chunks. The graph edges define relationships between these nodes, mapping hierarchical classifications and entity associations. This structured representation provides the deterministic foundation necessary for accurate information retrieval.

Database schema and resource costs

The database schema establishes strict boundaries for the RAG discovery process. Nodes capture specific conditions and map them hierarchically to established ontologies, while author and journal nodes provide provenance for published research. Lengthy documents are broken down into digestible text segments using Amazon Bedrock Knowledge Base chunking strategies, and specific classification nodes anchor unstructured textual data to standardised diagnostic metrics.

Operating this graph architecture requires specific cloud resource allocations. A standard Amazon Neptune Analytics graph running with 16 provisioned memory units incurs operational costs of $0.48 per hour. Development environments, such as Amazon SageMaker Jupyter notebooks running on t3.medium instances, add baseline compute and storage expenditures. Organisations must also factor in dynamic token consumption costs generated by the Amazon Bedrock Claude 4.5 Sonnet model during query processing and abstract generation.

Query execution and entity linking

The GraphRAG toolkit acts as the execution layer between the user interface and the underlying database. A dedicated Knowledge Graph Linker processes incoming natural language queries, extracts relevant entities using fuzzy string indexing, and maps them to established graph nodes. The system traverses the network pathways to generate plausible relational links before drafting a response through the Bedrock-hosted language model.

Retrieval accuracy depends on the entity matching configuration. An EntityLinker component aligns natural language terms from user prompts to the structured data schema. This fuzzy matching process handles the inherent noise and varied terminology found in complex enterprise datasets, ensuring users retrieve the correct nodes even when using imprecise language.

Modularity and system architecture

Data extraction relies heavily on specialised AI parsing. The architecture employs Claude to evaluate raw source documents and generate concise abstracts. Domain-specific tools then map these complex textual descriptions to standardised taxonomies.

The GraphRAG Python toolkit initialises a BedrockGenerator to power natural language interactions, while engineers configure a Knowledge Graph Linker component to bind the graph store to the language model. This integration creates a direct interface for executing queries and generating responses grounded strictly in the available graph data.

The architecture separates three core functions: language model initialisation, graph interfacing, and entity linking. Because the system is modular, teams can swap out the language model or tweak the graph structure without having to tear down and rebuild the whole application.

Performance metrics and real-world impact

Active deployments of the Neptune and Bedrock architecture return exact, verifiable citations for every generated answer. The system maps the entire reasoning path, displaying the specific graph traversal steps used to reach a conclusion.

Key performance metrics from early enterprise adopters include:

  • 87 percent reduction in research cycle durations — initial discovery phases that previously required six months now conclude in three weeks
  • 85 percent improvement in data retrieval speeds, directly supporting faster hypothesis testing
  • 70 percent drop in research review times due to automated citation mapping and source verification

Engineering teams can integrate new public databases or internal notes into the existing graph structure without disrupting active query interfaces. For governance and compliance, exact evidence trails required for regulatory submissions are captured, with graph traversal visualisations proving precisely how an AI model connected complex variables. Teams can trace every output directly to source documents, fulfilling compliance requirements for scientific integrity.

Maintaining a centralised knowledge graph also stops data decay. When senior scientists resign, their tacit knowledge regarding system behaviours or failed experiments remains indexed within the Neptune database. New personnel can query the system to review past decisions and instantly access the historical context of an ongoing project.

As GraphRAG frameworks mature, this AWS GraphRAG deployment model is unlikely to remain confined to pharmaceutical research. The ability to deterministically map internal, unstructured data against verified public repositories provides a blueprint for any enterprise struggling to extract actionable intelligence from fragmented legacy systems.

See also: Insilico Medicine advances AI drug for IPF to Phase III trials

Want to learn more about AI and big data from industry leaders? Check out AI & Big Data Expo taking place in Amsterdam, California, and London. The comprehensive event is part of TechEx and is co-located with other leading technology events including the Cyber Security & Cloud Expo.

Continue Reading

Artificial Intelligence

XDOF, three months out of stealth, is already closing in on a $1.2B Series B

Published

on

XDOF Series B

From stealth to unicorn talk in record time

Three months. That’s how long XDOF has been out in the open. And already, the robotics data startup is in late-stage conversations to raise a Series B at a valuation hovering around $1.2 billion, according to multiple sources familiar with the negotiations. The round would be led by 8VC.

Not bad for a company that didn’t even exist publicly until June.

XDOF was co-founded in 2024 by UC Berkeley researchers Philipp Wu (CEO) and Fred Shentu (CTO). Their origin story traces back to a research project called GELLO — a low-cost teleoperation system that lets a human operator control a robotic arm from a distance. The goal? Generate training data for robots. That work produced an influential paper in robotics and, eventually, a company.

The startup’s Series A, a $70 million round announced in June, drew participation from Thrive Capital, Andreessen Horowitz, Lux, and Spark Capital. At the time, XDOF wasn’t planning to raise again so soon. But the market had other ideas.

Why investors are knocking on XDOF’s door

The reason for the sudden interest? Growth. Real, measurable growth.

XDOF’s annualized revenue is approaching $50 million, sources say. That kind of traction, so soon after a Series A, tends to make venture capitalists sit up and take notice. It also tends to make them pick up the phone.

“They weren’t out raising,” one person familiar with the situation told TechCrunch. “The VCs came to them.”

Terms aren’t final, and the total capital being raised remains unclear. TechCrunch couldn’t confirm whether the $1.2 billion valuation includes the new funding or sits on top of it. Both XDOF and 8VC declined to comment.

The Scale AI for physical robots

XDOF’s pitch is straightforward: it builds the data pipelines, collection tools, and annotation systems that frontier AI labs and robotics companies would rather not build themselves. Think of it as an outsourced data-supply chain for the robotics industry.

Investors describe XDOF as the Scale AI or Mercor of physical robotics — a nod to the data-labeling giants that powered the AI boom. The comparison makes sense. Large language models trained on the entire internet. Physical robots? They don’t have that luxury. There’s no massive, ready-made dataset of real-world robot interactions sitting online. That scarcity makes data collection the critical bottleneck on the road to general-purpose machines.

Wu felt that bottleneck firsthand as a PhD student. His research on how robots learn from large datasets kept hitting the same wall: “large-scale data to work with” simply didn’t exist, he told TechCrunch in June.

Building the ABC dataset

XDOF is tackling that problem head-on. The startup is partnering with UC Berkeley’s AI Research lab to release what it believes is the largest collection of high-quality robot training data ever assembled. The dataset is called ABC.

Collecting that data requires a hybrid approach. XDOF combines remote robot teleoperation with human collectors who wear sensors to record everyday tasks. Think folding clothes. Flattening boxes. The mundane, physical chores that robots still struggle to master.

The company plans to hire and train teams of data collectors around the world. Two main roles are emerging:

  • Teleoperators who steer robots remotely to demonstrate tasks
  • Egocentric operators who wear body sensors to capture natural movement data

Early traction and the competitive landscape

XDOF has already signed up 20 customers, including several frontier AI labs, according to previous statements to TechCrunch. That customer base, combined with the revenue trajectory, helps explain the valuation chatter.

But XDOF isn’t alone in this niche. Other startups chasing real-world data for robot training include Mecka AI. And the human-data platforms that started with LLMs — like Scale AI and Micro1 — are expanding beyond text and images into physical domains.

The race to build the data infrastructure for physical AI is heating up. Whoever wins it will effectively control the fuel supply for the next generation of robots. That’s a position worth paying up for.

Whether the $1.2 billion valuation holds remains to be seen. Deals at this stage can shift. But the fact that XDOF is even in this conversation — three months after emerging from stealth — says something about the demand for what it’s building.

For more on how data is shaping the future of AI, check out AI data labeling trends and robotics funding rounds in 2024.

Continue Reading

Artificial Intelligence

New York City Pulls AI From Younger Classrooms—Here’s Why It Matters

Published

on

NYC AI ban

New York City Just Hit Pause on AI in Classrooms

New York City Public Schools is drawing a hard line: no generative AI for students from 2-K through eighth grade during the 2026-2027 school year. That’s over half a million kids walking into classrooms next week without access to AI-powered tools.

The district says it will remove software with student-facing AI features and block AI companion chatbots. High schoolers? They’re exempt. This isn’t a blanket ban—it’s a targeted move to decide when kids should actually start using the technology.

Mayor Zohran Mamdani put it bluntly: “The tech industry wants us to believe that AI-powered early education is not only inevitable, but necessary. We do not see it that way.”

Why NYC Is Worried About AI for Younger Students

The fear isn’t just that a kid will ask ChatGPT to write an essay. City officials want younger students to build core skills—critical thinking, creativity, communication—without leaning on AI as a crutch. They’re also pushing for stronger human connections in classrooms, not another screen.

Schools Chancellor Kamar Samuels said the city refuses to assume that innovation automatically equals more technology in front of students. It’s a deliberate slowdown, and it follows last year’s bell-to-bell cellphone ban that already limits device use during school hours.

What Happens When Kids Reach High School?

AI doesn’t vanish once students hit ninth grade. Instead, the district plans to roll out AI literacy classes twice a year. The goal? Teach teenagers how to think critically about the technology before they become dependent on it.

That’s a different approach from just saying no. It’s about timing—letting younger minds develop without AI, then giving older students the tools to question it.

The National Battle Over AI in Education

NYC’s decision sits at the center of a much bigger fight. The White House has pushed educators to embrace AI responsibly. Some teachers already use it to craft lesson plans, give feedback, or break down tough subjects. But not everyone’s on board.

The Department of Health and Human Services recently gathered childhood experts to talk about excessive screen time. Officials have also called for tougher safeguards around social media and AI. The message? Kids are spending too much time in front of screens, and AI might make it worse.

A Bold Experiment With Zero AI

Here’s what makes NYC’s move so interesting: instead of asking how much AI younger students should use, the largest school district in the country is starting with none. For one academic year, they’re testing whether classrooms are better off with AI kept outside the door.

That’s a radical stance, and it’s not without critics. Some educators argue AI can personalize learning or help struggling students catch up. But NYC is betting that a year without AI will reveal what kids actually need—not what tech companies think they need.

What This Means for Parents and Teachers

If you’re a parent in NYC, expect changes. AI-based apps may disappear from your child’s school day. Teachers will need to plan lessons without generative AI tools. And students in grades 2-K through 8 will rely more on traditional methods—paper, pencils, and human interaction.

For teachers elsewhere, this could be a signal. NYC is the biggest district to take this stance, and its findings could shape policies nationwide. The next year will be watched closely by educators, policymakers, and tech giants alike.

What Happens Next?

The district will spend the year studying how generative AI affects students before deciding what comes next. That research could lead to a permanent ban, a partial rollout, or something entirely different.

For now, NYC is making a statement: childhood shouldn’t be an AI beta test. Whether that’s the right call or a step backward, we’ll know more in 2027. Until then, the debate over AI in schools just got a lot more interesting.

If you’re curious about how AI is shaping other areas, check out our take on AI in education trends or classroom technology policies.

Continue Reading

Artificial Intelligence

Meta’s Muse Spark 1.3 takes on GPT-5.6 and Claude — but can it really win?

Published

on

Muse Spark 1.3

Meta just fired a serious shot in the AI arms race

The company quietly unleashed Muse Spark 1.3, its most advanced AI model to date, and it’s aiming straight at the top dogs. Developers can already access and pay for the update, which Meta says represents a massive leap forward in performance.

It won’t stay confined to the developer sandbox for long. Over the coming weeks, the model will roll out across Instagram, Facebook, and the Meta AI assistant — putting it in front of billions of everyday users.

What makes Muse Spark 1.3 actually different?

Meta’s Chief AI Officer, Alexandr Wang, didn’t mince words. He called this “the biggest jump so far on model performance,” pointing to serious gains in two areas: coding and agentic tasks — the kind where the AI acts on your behalf rather than just answering questions.

But here’s the catch. Wang told Bloomberg that Muse Spark 1.3 is competitive with Anthropic’s Claude Fable 5.1 and even beats OpenAI’s GPT-5.6 Sol at coding. That’s a bold claim, especially with OpenAI’s upcoming Astra model lurking in the wings.

Take those comparisons with a grain of salt, though. Benchmarks can be gamed, and a model that crushes one test might stumble on a totally different task. Real-world performance is what actually matters.

Efficiency gains under the hood

Wang broke down a few upgrades that set Muse Spark 1.3 apart:

  • 25% fewer tokens needed to complete the same job — meaning lower costs and faster responses
  • Multi-workflow handling — it can juggle several tasks at once instead of forcing separate sessions
  • Better context retention across long, complicated instructions
  • Self-awareness of limits — the model now pauses to ask for clarification before taking any irreversible action

That last point is quietly important. AI that knows when it doesn’t know is a big step toward trustworthiness, especially for agentic use cases.

Pricing stays flat, adoption explodes

Here’s something developers will appreciate: Meta isn’t raising prices. Muse Spark 1.3 costs the same as its predecessor, Muse Spark 1.2. That’s a smart move when rivals are hiking rates.

Wang told Bloomberg that adoption on Meta’s developer platform has been strong — some users are burning through trillions of tokens every week. Those numbers suggest real usage, not just hype.

What about open-source fans? Meta hasn’t decided whether it will release the model’s weights — the blueprint that lets outside developers build on top of it. The older Muse Spark 1.2 weights are still headed for release, but the new model’s future remains unclear.

The bigger picture: Meta’s spending spree continues

Meta is still pouring billions into AI infrastructure, and Muse Spark 1.3 is the clearest signal yet that the company believes it’s closing the gap with OpenAI and Anthropic. Whether that’s true or just corporate bravado will play out in the benchmarks and real-world deployments over the coming months.

For now, the model is available to developers, and the app rollout is imminent. If you’re building on Meta AI tools, this update is worth a serious look. And if you’re just a curious user, you’ll likely meet Muse Spark 1.3 in your Instagram feed sooner than you think.

One thing’s certain: the AI race just got a lot more interesting.

Continue Reading

Trending