الإجابة عن سؤال عبر مستندات ثنائية اللغة

المشكلة

Enterprise teams needed a reusable way to ask Arabic and English questions over private documents while keeping source control, predictable answers, and deployment flexibility. Those requirements normally conflict: the fastest route to good answers is a hosted model with a large context window, which is precisely what an organisation with private documents and infrastructure constraints cannot adopt. Each customer therefore rebuilt the same pipeline against its own language, cost, latency, and hosting limits.

ما بنيناه

We developed a document question-answering pipeline covering extraction, cleaning, chunking, embedding, vector search, prompt assembly, answer generation, and citations, with the model and retrieval components independently replaceable to suit a given customer's infrastructure.

ما توقّف عليه

Treating preprocessing, metadata filtering, retrieval evaluation, and bounded prompts as independent controls - rather than leaning on a larger context window - is what allowed a weak component to be swapped for a particular language, document type, latency target, or deployment environment without rebuilding the pipeline around it.