Entity-Guided Graph Traversal for KB-QA

• Entity-Guided Graph Traversal is a KB-QA method that uses detected entities to extract local subgraphs and map natural language queries into graph traversal operations.
• It integrates entity linking, subgraph extraction, and joint semantic mapping with predicate similarity and type constraints to effectively resolve disambiguation.
• The approach demonstrates improved recall and F1 on non-aggregation questions, streamlining query translation in large graph-structured knowledge bases like DBpedia.

Entity-Guided Graph Traversal is a knowledge base question answering (KB-QA) methodology that leverages local graph substructures, anchored on detected entities, to enable semantic parsing and answer retrieval from large graph-structured resources such as DBpedia. This approach is specifically suited for non-aggregation questions, focusing on mapping natural language questions into subgraph traversal operations that yield accurate answers while jointly resolving semantic mapping and disambiguation.

1. Knowledge Base and Formal Problem Definition

Let the underlying knowledge base (KB), such as DBpedia, be modeled as a directed, labeled graph $G = (V, E)$, where $V$ denotes the set of RDF nodes (resources, classes, literals), and $E \subseteq V \times P \times V$ is the set of labeled edges (each $(u,p,v) \in E$ encodes a relation $u\ \xrightarrow{p}\ v$). Given a user query $q$ in natural language, the system must return the accurate set of answers by traversing appropriate paths in $G$.

The entity-guided method proceeds by:

• Detecting a subset of KB entities $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$ referenced in $q$, each corresponding to a DBpedia URI.
• Extracting a “topological structure” or pattern $T_q$ from $V$0, represented as a tree with edges labeled by surface phrases (e.g., “mayor of”).
• Defining $V$1 as the maximal branch length (in edges) in $V$2, restricting traversal depth.

2. Entity Detection and Local Subgraph Construction

2.1 Entity Linking

The process employs an external entity linker (specifically, Wikipedia Miner), which:

• Identifies mention–resource pairs $V$3 in $V$4.
• Retains only those with linker score $V$5 ($V$6).
• Excludes schema-level (e.g. dbo:Actor) or category entities, retaining only instance-level entities for $V$7.

2.2 Subgraph Extraction

With $V$8 established, a local subgraph $V$9 is constructed as follows:

1. Initialize $E \subseteq V \times P \times V$0, $E \subseteq V \times P \times V$1.
2. For every $E \subseteq V \times P \times V$2 and for $E \subseteq V \times P \times V$3:
   • Perform breadth-first expansion to depth $E \subseteq V \times P \times V$4.
   • Collect all edges $E \subseteq V \times P \times V$5 with $E \subseteq V \times P \times V$6 or $E \subseteq V \times P \times V$7.
   • Augment $E \subseteq V \times P \times V$8 and $E \subseteq V \times P \times V$9 with endpoints and edges.
3. Expand until reaching depth $(u,p,v) \in E$0 (the longest path indicated by $(u,p,v) \in E$1). This design guarantees that any answer path conforming to $(u,p,v) \in E$2 lies entirely in $(u,p,v) \in E$3.

3. Joint Semantic Item Mapping and Disambiguation

Entity-guided graph traversal unifies two typically disjoint subtasks: (a) Semantic-Item-Mapping: Extract the structured template $(u,p,v) \in E$4, e.g., discerning the pattern "Who is the mayor of Berlin?” as ANSNODE—“mayor of”—Berlin, where ANSNODE is a variable for the answer; (b) Semantic-Item-Disambiguation: Select, within $(u,p,v) \in E$5, the precise sequence of predicates and nodes realizing the intended query semantics.

The methodology:

• Adopts light-weight constituency-based patterns to extract $(u,p,v) \in E$6 from $(u,p,v) \in E$7 (eschewing template induction).
• Searches $(u,p,v) \in E$8 for candidate paths matching the topology of $(u,p,v) \in E$9.
• Scores each candidate path based on the semantic match between KB predicate labels and question phrases, and enforces answer type constraints.

For a pattern $u\ \xrightarrow{p}\ v$0 with $u\ \xrightarrow{p}\ v$1 edges, each labeled $u\ \xrightarrow{p}\ v$2 (the $u\ \xrightarrow{p}\ v$3-th surface phrase), candidate paths $u\ \xrightarrow{p}\ v$4 in $u\ \xrightarrow{p}\ v$5 are scored:

$u\ \xrightarrow{p}\ v$6

where

• $u\ \xrightarrow{p}\ v$7 is the semantic similarity between predicate label $u\ \xrightarrow{p}\ v$8 and surface phrase $u\ \xrightarrow{p}\ v$9;
• $q$0 assesses the compatibility of terminal node $q$1 with the expected answer type inferred from question focus (e.g. "person", "place").

This joint objective disambiguates both predicate path selection and answer candidate typing.

4. Path Traversal Algorithm and Pruning

The core traversal algorithm, denoted "FindCandidatePaths," operates as follows for pattern length $q$2 and phrase set $q$3:

1. Initialize $q$4
2. For each step $q$5:
   • For each $q$6 path, score_so_far$q$7:
     • Enumerate top-$q$8 outgoing edges from $q$9 by $G$0.
     • Prune edges with similarity $G$1.
     • For each permissible edge, create new partial path in $G$2.
3. After $G$3 steps, $G$4 contains valid, length-$G$5 candidate paths.
4. Each $G$6 is scored with $G$7, yielding final path score.
5. Return candidates ranked by total score.

The state per traversal step is a triple: (current node $G$8, accumulated predicates, similarity score). Branching is curtailed by top-$G$9 predicate selection and threshold $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$0. In the worst case, the number of paths is $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$1 (for average branching factor $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$2), but effective pruning ensures tractable computational cost.

5. Path Scoring and Answer Selection

5.1 Predicate-Similarity Features

For each path edge $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$3 and corresponding $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$4, the system computes: $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$5 where $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$6 is a word similarity service.

5.2 Type-Constraint Feature

A focus phrase $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$7 is extracted from $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$8, typically the head noun following interrogatives. For each answer candidate $E_q = \{e_1, e_2, \ldots, e_k\} \subseteq V$9, the best semantic match is computed: $q$0

5.3 Combined Scoring

$q$1

with $q$2 the predicate scores and $q$3 the type score. Candidates are returned ranked by this measure.

6. Query Translation and System Output

While the implementation yields URI or literal answers directly, any discovered path $q$4 can be rendered as a SPARQL query:

$q$8 The OPTIONAL-FILTER clause encodes the type constraint derived from the focus phrase.

7. Experimental Evaluation and Comparative Performance

Experiments were conducted on QALD-3 benchmarks:

• The full test set contains 99 natural-language questions; QALD-3-NA is a non-aggregation subset (61 questions, excluding COUNT/ORDER BY/FILTER types).
• Metrics: Precision $q$5, Recall $q$6, F1 ($q$7), reported as averages.

Summary of results:

Dataset	System	Processed	Correct	Partial	Avg-Recall	Avg-Prec	Avg-F1
QALD-3-NA	Ours	53	30	13	0.67	0.61	0.61
	gAnswer demo	38	21	7	0.41	0.45	0.42
QALD-3-full	Ours	60	31	17	0.46	0.40	0.40
	gAnswer	76	32	11	0.40	0.40	0.40
	DEANNA	27	21	0	0.21	0.21	0.21

Entity-guided graph traversal achieves higher recall and F1 on non-aggregation questions compared to several state-of-the-art systems and leads on recall in the full QALD-3 evaluation set. This suggests its effectiveness in answer retrieval where explicit aggregation is not required and where local subgraph patterns, seeded by confidently linked entities, are salient.

8. Significance, Limitations, and Applicability

Entity-guided graph traversal simplifies the process of mapping questions to queries by:

• Avoiding heavy template induction (and thus manual engineering).
• Focusing on answer path ranking rather than exhaustive global search.
• Enabling joint semantic matching and type-based answer disambiguation within manageable subgraphs.

A plausible implication is that the method is less suited to questions which require aggregation, counting, or global reasoning over the KB. Its computational efficiency depends critically on the effectiveness of entity linking, the restrictiveness of local subgraph expansion, and the suitability of the underlying similarity metrics. The approach is well-aligned with KBs that exhibit rich instance-level connectivity and clearly typed relations, such as DBpedia.