Concept knowledge architecture strategies
Parent: Research & Knowledge Tooling · Published reference · snapshot 2026-10-22
↓ Facts as markdownall context files
Source-anchored research for Concept knowledge architecture strategies. Run status: BUDGET_EXHAUSTED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Structure and components
- AIS evaluates whether a generated statement is attributable to identified parts of an underlying source corpus. (low confidence) [source]
- AIS permits support from multiple source parts combined through reasoning such as arithmetic. (low confidence) [source]
- TREC test collections contain a document corpus, information needs, and relevance judgments. (low confidence) [source]
How it works
- Bitemporal history separates when a fact applies in the modeled world from when the system recorded it. (medium confidence) [source]
- ALCE assigns statement-level citation recall only when the cited passages jointly entail the whole statement. (low confidence) [source]
- ALCE's automatic precision method can falsely penalize a citation that partially supports a statement when other citations also cover that information. (low confidence) [source]
- Claimify can decline extraction when context does not resolve competing interpretations with sufficient confidence. (low confidence) [source]
- The late-chunking paper finds no benefit when surrounding document text is irrelevant to the target information. (low confidence) [source]
- Long late chunking uses overlapping long-context windows when the document exceeds the embedding model's context capacity. (low confidence) [source]
- During screening, true recall remains unknown until all candidate documents have been assessed because the total relevant-document count is unknown. (low confidence) [source]
- The query embedding model must match the intended stored embedding space when switching indexes. (medium confidence) [source]
- BEIR selected nDCG because it accommodates binary and graded relevance while respecting rank. (low confidence) [source]
- NIST requires the document collection and relevance-judgment set to match when evaluating a run. (low confidence) [source]
- Bruch et al. reduce evaluation cutoff for small corpora because recall at 1000 approaches one across methods. (low confidence) [source]
Measurements and reference values
- OpenSearch's six-dataset comparison reported RRF nDCG@10 averaging 3.86% below its score-based hybrid comparator. (low confidence) [source]
Problems, failure modes and limitations
- Elasticsearch alias actions can partially succeed unless the request requires missing aliases to fail the complete action list. (low confidence) (verified as of 2026-10-22) [source]
Comparisons and alternatives
- PROV validity checks a consistent provenance history rather than establishing the factual truth of its assertions. (low confidence) [source]
- The RRF rank constant differs from a nearest-neighbor count or a candidate-depth limit. (low confidence) [source]
- DnDScore verifies a specified atomic subclaim with separate contextual information instead of treating all added context as the target claim. (low confidence) [source]
- Claimify's evaluation framework assesses element-level coverage of verifiable information, rather than only whether a sentence produces any claim. (low confidence) [source]
- WiCE preserves alternative sufficient supporting-sentence sets rather than requiring one unique evidence set. (low confidence) [source]
- Anthropic reports limited gains from generic document summaries added to chunks, unlike its chunk-specific context. (low confidence) [source]
- SAFE explicitly presents its numerical percentages and record counts as adaptable examples rather than universally applicable rules. (low confidence) [source]
- Elasticsearch 8.19 reindexing reads a source snapshot, rather than continuously applying later writes. (low confidence) [source]
- BEIR evaluates retrieval over heterogeneous tasks and domains rather than one homogeneous question-answering setting. (low confidence) [source]
Facts and statements
- PROV represents a revised document as an entity derived from an earlier document entity. (medium confidence) [source]
- A retrospective correction changes the current account of valid history while preserving earlier recorded beliefs. (medium confidence) [source]
- Valid time can describe a future-effective change recorded before that change takes effect. (low confidence) [source]
- XTDB's ordinary query defaults to current valid time and the best currently known system-time view. (low confidence) (verified as of 2026-10-22) [source]
- An audit query can select a past system time to exclude corrections learned later. (low confidence) [source]
- PROV entities have fixed aspects; changing an aspect can require a different entity. (medium confidence) [source]
- The temporal database glossary distinguishes uncertain valid time from transaction time maintained by the database. (low confidence) [source]
- A fact transferred between databases can carry several transaction-time histories. (low confidence) [source]
- Different modeled perspectives can assign different valid times to the same fact. (low confidence) [source]
- XTDB v1's bitemporality does not itself implement persisted-query replay and cascading retroactive corrections. (low confidence) [source]
- An immutable record of an action's inputs can satisfy some audit needs without a complete bitemporal property history. (low confidence) [source]
- PROV quotation describes copied content, whereas revision describes a revised version of an earlier entity. (low confidence) [source]
- XTDB provides ERASE for hard deletion of history; ordinary historical retention is therefore not an unconditional permanence guarantee. (low confidence) (verified as of 2026-10-22) [source]
- RRF adds reciprocal rank contributions from the input rankings; raw score magnitudes do not enter its formula. (high confidence) [source]
- In truncated-list RRF, an item absent from one input list contributes zero from that list. (low confidence) [source]
- Cormack et al. fixed k=60 during a pilot and retained it during later validation. (low confidence) [source]
- Elastic's 2023 BEIR subset experiment favored k=20 and candidate depth 1000 for the tested dense retrievers. (low confidence) [source]
- Bruch et al. found tuned convex score combination superior to RRF in their in-domain and out-of-domain experiments. (low confidence) [source]
- Elasticsearch separates the per-retriever rank window from the final response size. (low confidence) (verified as of 2026-10-22) [source]
- Bruch et al.'s min-max normalization uses the minimum and maximum scores in the retrieved candidate union. (low confidence) [source]
- Bruch et al. compute missing candidate scores and approximate otherwise unknown ranks within the candidate union. (low confidence) [source]
- Increasing the RRF rank constant flattens relative differences between high and low ranks. (low confidence) [source]
- Bruch et al. exclude near-zero score variance from their empirical normalization analysis and identify it as a challenge for some normalizers. (low confidence) [source]
- The original RRF definition models each input ranking as a permutation, with one rank per document. (low confidence) [source]
- The original RRF experiments include a TREC-3 case where CombMNZ outscored RRF, so the paper does not show universal dominance. (low confidence) [source]
- Elasticsearch requires a fixed rank window for stable RRF pagination; changing that window can change previously seen ordering. (low confidence) (verified as of 2026-10-22) [source]
- Exact-term matching depends on indexed field analysis; Elasticsearch's standard text analyzer removes most punctuation and lowercases tokens. (low confidence) (verified as of 2026-10-22) [source]
- Bruch et al.'s normalization rank-equivalence result for one query does not by itself establish equivalent learned weights across all queries. (low confidence) [source]
- Azure documents a fused RRF score bound that increases with the number of query lists being fused. (low confidence) (verified as of 2026-10-22) [source]
- Azure semantic reranking runs after RRF and reports its score separately from the fusion score. (low confidence) (verified as of 2026-10-22) [source]
- The EAHR preprint bounds unread RRF contributions and requests deeper channel ranks while they can change complete-list top-K membership or order. (low confidence) [source]
- EAHR's reported anti-correlated cases exhaust both input lists; its authors do not guarantee a speedup on every request. (low confidence) [source]
- AIS treats whether a source is correct or trustworthy as a separate evaluation from whether the generated text accurately represents it. (low confidence) [source]
- FActScore computes the fraction of a generation's atomic facts that a reliable knowledge source supports. (low confidence) [source]
- ALCE's citation-precision evaluation penalizes irrelevant citations without requiring the citation set to be minimal. (low confidence) [source]
- ALCE evaluates fluency, correctness, and citation quality as separate dimensions. (low confidence) [source]
- AIS resolves a sentence's interpretation using its linguistic context and the relevant time before judging attribution. (low confidence) [source]
- FActScore does not measure factual recall and does not penalize a response merely for providing fewer facts. (low confidence) [source]
- FActScore's authors exclude nuanced, debatable facts and frequently conflicting knowledge sources from the metric's stated applicability. (low confidence) [source]
- Wallat and colleagues define citation faithfulness to require causal influence from the cited document in addition to citation correctness. (low confidence) [source]
- Their proposed necessary-condition tests include altering cited information and adding irrelevant documents while examining the answer and attribution. (low confidence) [source]
- DnDScore identifies a tension between isolating atomic subclaims and adding the context needed to interpret them. (low confidence) [source]
- Decomposition Dilemmas identifies harmful decomposition errors including omitted context, over-decomposition, ambiguity, and alteration of the original meaning. (low confidence) [source]
- WiCE annotates supported, partially supported, and not-supported claims and subclaims. (low confidence) [source]
- Voyage contextualized embedding accepts grouped chunks so each chunk is encoded with its document peers. (low confidence) (verified as of 2026-10-22) [source]
- Voyage contextualized embedding preserves chunk order in the returned document embeddings. (low confidence) (verified as of 2026-10-22) [source]
- Voyage supports query and document input types that add task-specific prompts before embedding. (low confidence) (verified as of 2026-10-22) [source]
- Anthropic contextual retrieval prepends chunk-specific explanatory context before embedding and BM25 indexing. (low confidence) [source]
- Late chunking contextualizes document tokens before pooling token spans into individual chunk vectors. (low confidence) [source]
- Dense X defines propositions as minimal facts that include the context required to interpret them independently. (low confidence) [source]
- Late chunking can be applied to suitable long-context embedding models without additional training. (low confidence) [source]
- Dense X reports retrieval and QA improvements from proposition units under its evaluated computation budgets. (low confidence) [source]
- Chunk boundaries, size and overlap remain empirical design choices in Anthropic's contextual retrieval recipe. (low confidence) [source]
- Dense X's evaluated retrieval corpus is Wikipedia, limiting direct evidence about other corpora. (low confidence) [source]
- The late-chunking paper's overlap ablation does not show a clear retrieval advantage from overlapping chunks. (low confidence) [source]
- Dense X's manual proposition audit found both unsupported propositions and propositions lacking standalone context. (low confidence) [source]
- Callaghan and Müller-Hansen formulate stopping as rejecting a null hypothesis that achieved recall is below a chosen target. (low confidence) [source]
- Their random-sampling criterion uses a hypergeometric model for relevant records drawn without replacement from the finite unscreened pool. (low confidence) [source]
- SAFE combines random training-set screening, active learning, a different screening model, and a final quality-check phase. (low confidence) [source]
- Callaghan and Müller-Hansen report inconsistent achieved recall and work reductions across datasets for previously proposed stopping methods. (low confidence) [source]
- The 2024 stopping-criteria commentary warns that observed reliability can depend on datasets, ranking algorithms, hyperparameters, and implementation details. (low confidence) [source]
- SAFE warns that using expert-selected key papers as training seeds can bias the screening model. (low confidence) [source]
- The SAFE paper states that it does not present a direct comparison with existing stopping heuristics. (low confidence) [source]
- Guest, Namey, and Chen calculate new information over consecutive observation runs relative to unique themes in a specified initial base. (low confidence) [source]
- Guest, Namey, and Chen explicitly state that their new-information thresholds lack a probability-theory guarantee of saturation. (low confidence) [source]
- Their saturation method was tested on single-tier codebooks; hierarchical applications require choosing which coding level contributes to the calculation. (low confidence) [source]
- Hennink, Kaiser, and Marconi distinguish code saturation, where new issues stop appearing, from meaning saturation, where new dimensions of issues stop appearing. (low confidence) [source]
- In the Hennink, Kaiser, and Marconi study, some conceptual codes reached meaning saturation between interviews 16 and 24, while the conceptual code responsibility for health never reached meaning saturation. (low confidence) [source]
- In that study, higher code prevalence did not indicate earlier meaning saturation. (low confidence) [source]
- Repke and colleagues evaluated stopping methods using 223 simulated screening runs over 81 real-world datasets. (low confidence) [source]
- In those experiments, CMH never stopped before the specified recall target, but often screened substantially beyond the optimal stopping point. (low confidence) [source]
- Repke and colleagues evaluate both missed recall targets and additional screening after the target's theoretically optimal stopping point. (low confidence) [source]
- Repke and colleagues disclose that evaluation co-author Finn Müller-Hansen also co-authored CMH. (low confidence) [source]
- Equal vector dimensions do not establish relevance compatibility between embeddings from different models. (low confidence) [source]
- Voyage documents compatibility within its voyage-4 model family while still recommending corpus regeneration during migration. (low confidence) (verified as of 2026-10-22) [source]
- MongoDB's self-managed migration procedure keeps new embeddings in a separate field while retaining the existing field and index. (low confidence) (verified as of 2026-10-22) [source]
- Qdrant supports building a second collection in the background before atomically changing its collection alias. (low confidence) (verified as of 2026-10-22) [source]
- Elasticsearch can remove and add an index alias in one atomic multi-action request. (low confidence) (verified as of 2026-10-22) [source]
- MongoDB recommends evaluating a successor embedding model on representative application data before production migration. (low confidence) [source]
- A successor model with a shorter input context can truncate text that the old model accepted. (low confidence) [source]
- SentenceTransformer can load a model at an explicit repository commit, tag or branch revision. (low confidence) (verified as of 2026-10-22) [source]
- SentenceTransformer's encoding interface exposes prompt, normalization, output precision and dimension truncation settings. (low confidence) (verified as of 2026-10-22) [source]
- Elasticsearch reindexing does not copy source index settings or mappings into the destination. (low confidence) (verified as of 2026-10-22) [source]
- Qdrant's migration tutorial warns that deleting a not-yet-backfilled point can let later backfill recreate it. (low confidence) (verified as of 2026-10-22) [source]
- Keeping the old Qdrant collection current during an observation period preserves rollback after the initial switch. (low confidence) (verified as of 2026-10-22) [source]
- Stopping writes to the old collection makes later rollback lose intervening changes. (low confidence) (verified as of 2026-10-22) [source]
- Qdrant's incremental update tutorial hashes normalized chunk text to distinguish changed content from unchanged content. (low confidence) (verified as of 2026-10-22) [source]
- Qdrant's incremental update tutorial separates a chunk's location-based point identifier from its content hash. (low confidence) (verified as of 2026-10-22) [source]
- BEIR found no retrieval approach consistently strongest on every included dataset. (low confidence) [source]
- TREC pooling combines top results from multiple runs for relevance assessment. (low confidence) [source]
- Traditional pooled evaluation often scores unjudged documents as nonrelevant. (low confidence) [source]
- BEIR's manual TREC-COVID hole annotation increased measured scores for non-lexical approaches. (low confidence) [source]
- A TREC-8 study found near-identical system rankings after adding relevance judgments for modern neural retrieval results. (low confidence) [source]
- trec_eval reciprocal rank measures the first relevant retrieved document and suits a user needing one result. (low confidence) [source]
- TREC separates the development period from evaluation data released without relevance labels. (low confidence) [source]
- Recall divides retrieved relevant items by all relevant items; precision and recall ignore their order. (low confidence) [source]
- BEIR's TREC-COVID hole assessors did not know which retrieval system supplied each judged result. (low confidence) [source]
- Upadhyay et al. report successful LLM hole filling in simulations that remove relevance judgments from three TREC DL datasets. (low confidence) [source]
- Soboroff argues that model-generated relevance labels make the model's judgments the evaluation target, limiting the evaluation's validity. (low confidence) [source]
- The TREC 2024 RAG assessment study found UMBRELA-based system rankings highly correlated with manual rankings across 77 submitted runs. (low confidence) [source]
- ALCE evaluates generated text on separate fluency, correctness, and citation-quality dimensions. (low confidence) [source]
- RAGAS separates relevant focused retrieval, faithful use of context, and generation quality as distinct evaluation dimensions. (low confidence) [source]
- MultiHop-RAG includes queries, answers, and supporting evidence so evidence retrieval and reasoning given evidence can be evaluated separately. (low confidence) [source]
- The original BEIR neural retrieval experiments use only the first 512 word pieces of each document. (low confidence) [source]
Children
- Temporal dependency invalidation (frontier)
- Uncertain temporal intervals (frontier)
- Evidence-source identity and ownership (frontier)
- Source-diverse evidence selection (frontier)
- Query-intent routing (frontier)
- Cross-encoder reranking (frontier)
- Causal attribution faithfulness (frontier)
- Evidence-set ranking for human verification (frontier)
- Hierarchical summary retrieval (frontier)
- Late interaction token retrieval (frontier)
- Contextualized embedding model training (frontier)
- Decision value of information (frontier)
- Living-review update triggers (frontier)
- Ordered change-data capture and tombstone replay (frontier)
- Approximate-vector quantization migration (frontier)
- Embedding drift detection (frontier)
- Temporal relevance evaluation (frontier)
- Evidence-set completeness (frontier)
- Judge calibration and disagreement (frontier)
- Bitemporal claim provenance
- Candidate-depth-aware hybrid rank fusion
- Citation entailment for generated research prose
- Context-preserving multi-granularity embeddings
- Marginal evidence gain research stopping
- Revision-bound embedding index migration
- Task-stratified retrieval evaluation