Klint (Knowledge Interator) is a web application designed to assist users creating RDF knowledge and queries using the FrameBase schema, and creating integration rules from other datasets into the FrameBase schema.

Modes

Klint has currently 3 working modes:

• Assisted Integration Mode. In this mode, you can introduce a RDF dataset (can be just the schema), give it a name and click the "process" button. Klint will generate complex integration rules, that can be edited. Nodes representing variables (in red) connect the source dataset subgraph (containing green nodes) and the FrameBase integrated subgraph (containing blue nodes). Klint is currently in beta. Because of performance limitations, only integration rules cached in the server can be accessed. The names for cached datasets are: dbpedia, wikidata, oxford.
• Visual Knowledge Building Mode. In this mode, you can build pieces of grounded knowledge (without variables) under the FrameBase schema.
• Visual Query Building Mode. In this mode, you can use variable nodes to build queries to retrieve knowledge that was modelled with FrameBase.

Visual graph editing (right pane)

A (subject,predicate,object) triple is represented by two links, one connecting the subject with the predicate, and another connecting the predicate with the object. Klint tries to represent the graph in a way that the links belonging to the same triple have similar orientations. Nodes acting as subjects or objects in a triple have a thicker border than the ones acting as predicates.

To create a triple: Click and drag to create the connection between the subject and the predicate of a triple, and do it again to create the connection between the predicate and the object.

To select a node, click on it. You can edit it in the left pane.

To create a new node, click on the canvas.

Hold the shift key to move a node around and lock its position. To free it, double click on it.

The color of the node indicates the type.

• Blue nodes represent FrameBase resources (frames and frame elements).
• Light blue nodes represent FrameBase resources (direct binary predicates).
• Green nodes represent resources from a source dataset (in Assisted Integration Mode).
• Red nodes represent free variables in a SPARQL query.
• Grey nodes represent resources that are not specific to FrameBase or the source, for instance RDFS resources.

Node editing (left pane)

There are different ways to edit a node in FrameBase:

• Using the search function in the top of the left pane. When searching for a node in FrameBase, you can include any number of the following selection flags:
  • #f Frames. Classes representing kinds of situations, events, processes, etc.
    • #micf Microframes. Frames with very specific meanings.
    • #minf Miniframes. Frames with more general meanings (grouping near-synonym microframes).
    • #macf Macroframes. Frames with the most general meanings (grouping microframes evoking related situations, but sometimes having very different or even opposite meanings).
  • #e Frame Elements. Properties belonging to frames
  • #dbp Direct Binary Predicates. Properties connecting directly the values of pairs of Frame Elements.
• Using auto-suggestions. This works like the search function, but the list of candidates is obtained automatically when certain nodes are selected, using the context of these nodes to search for suitable candidates. For instance, when selecting the node that is a property for an instance of a frame, the frame element properties for that frame will be suggested as candidates.
• Manually editing the identifier (IRI) and optionally the name in the bottom of the left pane. This is recommended for cases where an appropriate node is not found using the other methods.

A candidate entity for the value of a node can be used in two different ways:

• Using the button Apply, which assigns the value of the candidate entity to the selected node.
• For some candidate entities, the button IP (Instantiate Pattern), creates a subgraph around the selected node, that represents a common pattern where that entity is present. For instance, selecting IP for microframe entities, generates a frame instance with that microframe as type, and a few empty nodes that can be filled with frame element properties for that microframe.