Cost Characterization of Vertically Partitioned Federated Knowledge Graphs
Md Saikat Islam Khan Bappy, Oshani Seneviratne
cs.AI · cs.DB · cs.IR
Quick verdict
Four vertical KG-partitioning strategies compared on five costs, three shown invariant; careful, honest study, though tiny relation vocabularies limit reach.
Summary
The paper treats the distribution of a knowledge graph across autonomous organizations — a vertical partition where silos share entities but own disjoint relation subsets — as a data-management design problem. It formalizes relation-to-silo assignment and compares four strategies (semantic domain grouping, frequency balancing, co-occurrence graph-cut, random) along five cost metrics: communication, candidate index size, cross-silo path length (CSPL), load balance, and query latency. Three metrics prove invariant to the partition, reducing the design problem to a locality-versus-balance trade-off. Experiments on MetaQA (15 relations) and PathQuestion (13 relations) at 3, 5, and 7 silos hold a TransE-plus-frozen-BERT question-answering substrate fixed. At 3 silos on PathQuestion, the graph-cut strategy cuts the held-out crossing rate from 0.517 to 0.276 (47% lower than the inherited partition), while frequency balancing attains the lowest imbalance in all six dataset-silo combinations; the trade-off weakens as silo counts grow and relations per silo shrink. Key limitations: relation vocabularies under 20 leave large-vocabulary guidance conjectural; PathQuestion quality is only loosely matched (Hits@3 0.661–0.831), confounding its cost comparisons; BFS shortest-path recovery biases both the locality metric and the method optimizing it; and no statistical tests or variance estimates are reported beyond multi-seed averaging for the random strategy.
Review complete
Assessment at a glance
4
risk flags identified
● high 0
● medium 2
● low 2
5 strengths · 5 weaknesses · 5 author questions
AI text signal = Binoculars zero-shot detector score over 20 sampled passages (Fast-DetectGPT co-reported) — absence does not prove human authorship, and a flag does not imply misconduct.
Levels reflect verification complexity — not a quality score. Evolve never rates your paper.
Key claims under review
- Communication cost, candidate index size, and query latency are invariants of the graph and silo count, so the partitioning decision reduces to a two-axis trade-off between cross-silo path length (M3) and load balance (M4).
- At K=3 on PathQuestion, co-occurrence graph-cut partitioning lowers the held-out test crossing rate from 0.517 to 0.276 — a 47% reduction versus the inherited semantic-domain partition.
- Frequency-balanced partitioning achieves the lowest imbalance in all six dataset-by-silo-count combinations, and the locality-balance conflict weakens as silo count grows and relations per silo shrink.
- The governing quantity for which regime applies is relations per silo (|R|/K), though transfer of the two-regime picture to large vocabularies remains an unverified conjecture.
Strengths
Clean invariant identification reduces the design space
Section 4/Table 1 show M1 (Eq. 3), M2 (Eq. 4), and M5 are fixed by graph and silo count (M2: 144.3 and 103.6 entries per topic entity; M5: 10.5/10.0 ms), so partitioning collapses to the M3-vs-M4 trade-off — a genuinely useful simplification for practitioners.
Honest structural-versus-empirical bookkeeping
Section 6 explicitly separates arithmetic facts (Πdom's empty surplus silos; the ⌊1.25·|R|/K⌋ cap) from measured findings (the 47% crossing-rate cut), and self-declares PathQuestion quality as 'loosely matched' rather than hiding the confound.
Controlled substrate with a generalization check on locality
High reproducibility
Guidance tied to a governing ratio, not absolute K
Weaknesses
Toy-scale partitioning space
Quality confound on the headline benchmark
No statistical treatment
Self-referential path-recovery bias
M3's operational cost is not paid by the evaluated system
Full Review Report
$1.99 · one-timeUnlock the complete preliminary analysis Evolve produced for this paper.
Report preview
Scope & Claims
This DMKG'26 workshop paper asks a question adjacent to federated KG question answering: given a relation vocabulary split across K autonomous silos over a shared entity space, what does each relation-to-silo assignment cost? Section 3.1 formalizes vertical partitioning as Π: R → {1..K} with disjoint relation subsets; raw triples never cross silos. Four strategies are compared — semantic domain grouping (Πdom), greedy frequency balancing (Πfreq), co-occurrence graph-cut with an ε=1.25 slack cap (Πcut), and random (Πrand) — scored on five metrics (Table 1). The central reframing is defensible and useful: M1 (per-round communication, Eq. 3), M2 (pooled two-hop candidate index, Eq. 4), and M5 (latency) are invariant to the partition, collapsing the design problem to M3 (cross-silo path length, Eq. 5) versus M4 (imbalance, the CV of silo triple counts, Eq. 6). Claims are stated with unusual discipline: Section 6's 'What is structural and what is measured' separates arithmetic consequences (Πdom's empty surplus silos; the ⌊1.25·|R|/K⌋ cap) from genuinely empirical findings (the 47% crossing-rate cut).
The remaining sections cover Methodology Assessment, Statistical Evidence, Results & Reproducibility, Limitations & Risks, and Verdict & Recommendations.
- All 5 strengths & 5 weaknesses, analyzed in detail
- 4 risk flags with severity, section & reviewer questions
- Methods & statistical evidence assessment
- 5 questions a peer reviewer would ask
- Full six-dimension evaluation report & recommendations
One-time purchase · this paper only
One-time purchase, this paper only. AI-generated preliminary analysis — not peer review.
Frequently asked questions
What is a vertically partitioned federated knowledge graph?
A knowledge graph split across autonomous organizations that share the same entities but each own a disjoint subset of relations — for example, one party holds director facts, another holds actor facts about the same movies. No party holds the whole graph, raw triples never cross organizational boundaries, and answering multi-hop questions requires combining facts from several silos.
Which partitioning strategy should I choose for a federated knowledge graph?
According to this paper: co-occurrence graph-cut partitioning is best when each silo can hold several relations and cross-silo reasoning dominates (it cut the crossing rate from 0.517 to 0.276 on PathQuestion at 3 silos). Frequency-balanced partitioning is the safer choice when silos are numerous or throughput is bounded by the slowest silo — it had the lowest imbalance in all six tested combinations, and its locality disadvantage fades as silo counts grow.
Does partitioning affect query latency or communication cost in this setting?
No. Three of the paper's five metrics are invariant to the partition: per-round communication (0.27–0.62 GB depending only on silo count), candidate index size (144.3 entries per topic entity on MetaQA, 103.6 on PathQuestion), and mean query latency (about 10 ms on both benchmarks). Only cross-silo path length and load balance actually depend on how relations are assigned to silos.
Is code or data available for this partitioning study?
Yes. The partitioning algorithms, candidate index construction, and measurement harness are released at github.com/brains-group/vertical-fkg-partitioning, evaluated on the public MetaQA and PathQuestion benchmarks, with all hyperparameters and training configurations stated in the paper.
About this review
This is an AI-generated preliminary review by Evolve.Pub, produced from the openly available text of the paper. It is not peer review and does not represent the authors' views. The canonical record of the paper is at the publisher link above.
- Figures 1–6 are image content not recoverable from the text extraction; their takeaways were assessed from captions and body text only. Every number cited in this review comes from the body text and Tables 1–3, all of which extracted intact through the reference list.
Go deeper on this paper
Wrote a paper? Stress-test it before reviewers do.
Upload your manuscript for the same structured scrutiny — reasoning, statistics, evidence, figures, and reproducibility.
