Tensorflow implementation of the method PoLo from this paper.

This implementation is based on Shehzaad Dhuliawala's repository, which contains the code for the paper Go for a Walk and Arrive at the Answer - Reasoning over Paths in Knowledge Bases using Reinforcement Learning.

The dependencies are specified in requirements.txt. To run PoLo, use one of the config files or create your own. For an explanation of each hyperparameter, refer to the README file in the configs folder.

Then, run the command

./run.sh configs/${config_file}.sh

KG triples need to be written in the format subject predicate object, with tabs as separators. Furthermore, PoLo uses inverse relations, so it is important to add the inverse triple for each fact in the KG. The prefix _ is used before a predicate to signal the inverse relation, e.g., the inverse triple for Germany hasCapital Berlin is Berlin _hasCapital Germany.

Datasets should have the following files:

dataset
    ├── train.txt
    ├── dev.txt
    ├── test.txt
    ├── graph.txt
    └── rules.txt

Where:

train.txt contains all train triples.

dev.txt contains all validation triples.

test.txt contains all test triples.

graph.txt contains all triples of the KG except for dev.txt, test.txt, the inverses of dev.txt, and the inverses of test.txt.

rules.txt contains the rules as a dictionary, where the keys are the head relations. The rules for a specific relation are stored as a list of lists (sorted by decreasing confidence), where a rule is expressed as [confidence, head relation, body relation, ..., body relation].

For Hetionet, the complete graph is split into graph.txt (no inverse triples) and graph_inverses.txt (inverse triples) because of the file size constraints on GitHub.

For rules learned by the method AnyBURL, the script preprocess_rule_list.py can be used to preprocess the rules into the format that is needed for PoLo.

Finally, two vocab files are needed, one for the entities and one for the relations. These can be created by using the create_vocab.py file.