A knowledge graph display method and system

Abstract

The present application discloses a knowledge graph display method, the method comprising: obtaining the point edge information to be rendered of the knowledge graph to be displayed; in response to the determination instruction of the target layout type, generating a graph of the point edge information to be rendered according to the target layout type and the point edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types; determining the rendering type according to the number of points and edges of the points and edges to be rendered; rendering the graph of the point edge information to be rendered according to the rendering type to obtain a knowledge graph interface; and displaying the knowledge graph interface. It can be seen that the present application provides a plurality of preset layout types, and the user can flexibly select and switch according to the data structure, which can enrich the user's usage scenarios; the present application can determine the rendering type of the knowledge graph according to the number of points and edges of the point edge information to be rendered, so as to ensure that the knowledge graph interface can accommodate more nodes and edges, so that the user can intuitively obtain more available information on the graph.

Description

Technical Field

[0001] The present application relates to the field of knowledge graphs, and in particular to a knowledge graph display method and system. Background Art

[0002] With the vigorous development of knowledge graphs in various fields, more and more user groups are accustomed to displaying complex knowledge fields through data mining, information processing, knowledge measurement and graph drawing. However, the existing graph visualization components on the market have the following shortcomings: the layout display method is single, the layout cannot be selected, and the presentation effect cannot meet the actual business requirements; when the dynamic layout of the force-directed graph exceeds thousands of points, it is easy to freeze, and only one of the dynamic and static display effects of the force-directed graph is supported. In terms of visualization display, the current knowledge graph display method cannot meet user requirements. Summary of the invention

[0003] This application provides a knowledge graph display method to solve the following shortcomings of existing graph visualization components: single layout display mode, layout cannot be selected, and presentation effect cannot meet actual business requirements; force-directed graph dynamic layout is prone to freeze when it exceeds thousands of points, and only supports one of the dynamic and static display effects of force-directed graphs. .

[0004] In a first aspect, the present application provides a knowledge graph display method, the method comprising:

[0005] Get the vertex and edge information to be rendered of the knowledge graph to be displayed;

[0006] In response to a target layout type determination instruction, generating a graphic of the point edge information to be rendered according to the target layout type and the point edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types;

[0007] Determining a rendering type according to the number of the points and edges to be rendered;

[0008] Rendering the graph of the point-edge information to be rendered according to the rendering type to obtain a knowledge graph interface;

[0009] The knowledge graph interface is displayed.

[0010] In a second aspect, the present application provides a knowledge graph display device, the device comprising:

[0011] An acquisition unit, used to acquire the vertex and edge information to be rendered of the knowledge graph to be displayed;

[0012] A response unit, configured to respond to a target layout type determination instruction and generate a graphic of the point edge information to be rendered according to the target layout type and the point edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types;

[0013] A determination unit, configured to determine a rendering type according to the number of point edges to be rendered;

[0014] A rendering unit, used to render the graph of the point-edge information to be rendered according to the rendering type to obtain a knowledge graph interface;

[0015] A display unit is used to display the knowledge graph interface.

[0016] In a third aspect, the present application provides a knowledge graph display system, the system comprising: a task scheduler, a graph resource pool, a knowledge graph display platform, a knowledge database and an interface layer; wherein the knowledge database stores knowledge data to be displayed in the knowledge graph; the interface layer encapsulates a number of interfaces for accessing the knowledge database;

[0017] The task scheduler is used to obtain the to-be-rendered point edge information of the to-be-rendered knowledge graph in the knowledge database through the interface layer; in response to a target layout type determination instruction, generate a graph of the to-be-rendered point edge information according to the target layout type and the to-be-rendered point edge information; wherein the target layout type is one of a plurality of preset layout types; and store the graph of the to-be-rendered point edge information in the graph resource pool;

[0018] The knowledge graph display platform is used to read the graphics of the point-edge information to be rendered in the graph resource pool; determine the rendering type according to the number of points and edges to be rendered; render the graphics of the point-edge information to be rendered according to the rendering type to obtain a knowledge graph interface; and display the knowledge graph interface.

[0019] In a fourth aspect, the present application provides a readable medium comprising execution instructions. When a processor of an electronic device executes the execution instructions, the electronic device executes any method described in the first aspect.

[0020] In a fifth aspect, the present application provides an electronic device, comprising a processor and a memory storing execution instructions, wherein when the processor executes the execution instructions stored in the memory, the processor executes any method described in the first aspect.

[0021] It can be seen from the above technical solution that the present application provides a method for displaying a knowledge graph, the method comprising: obtaining the point and edge information to be rendered of the knowledge graph to be displayed; in response to the determination instruction of the target layout type, generating a graph of the point and edge information to be rendered according to the target layout type and the point and edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types; determining the rendering type according to the number of points and edges of the point and edge to be rendered; rendering the graph of the point and edge information to be rendered according to the rendering type to obtain a knowledge graph interface; and displaying the knowledge graph interface. It can be seen that the present application provides a plurality of preset layout types, and users can flexibly select and switch according to the data structure, which can enrich the user's usage scenarios; the present application can determine the rendering type of the knowledge graph according to the number of points and edges of the point and edge information to be rendered, so as to ensure that the knowledge graph interface can accommodate more nodes and edges, so that users can intuitively obtain more available information on the graph.

[0022] The further effects of the above-mentioned non-conventional preferred manner will be described below in conjunction with specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the embodiments of the present application or the existing technical solutions, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0024] Figure 1 A schematic diagram of a process for displaying a knowledge graph provided in one embodiment of the present application;

[0025] Figure 2 A schematic diagram of a layout selection interface provided by an embodiment of the present application;

[0026] Figure 3 A schematic diagram of a knowledge graph expansion interface provided in one embodiment of the present application;

[0027] Figure 4 A schematic diagram of a knowledge graph quick association interface provided in one embodiment of the present application;

[0028] Figure 5 A schematic diagram of a knowledge graph condition association interface provided in one embodiment of the present application;

[0029] Figure 6 A schematic diagram of a knowledge graph condition association interface provided in one embodiment of the present application;

[0030] Figure 7A schematic diagram of the structure of a knowledge graph display device provided in one embodiment of the present application;

[0031] Figure 8 A schematic diagram of the architecture of a knowledge graph display system provided in one embodiment of the present application;

[0032] Fig. 9 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0034] In the existing technology, with the vigorous development of knowledge graphs in various fields, more and more user groups are accustomed to displaying complex knowledge fields through data mining, information processing, knowledge measurement and graph drawing. However, the existing graph visualization components on the market have the following shortcomings: 1. The display method is single, the layout cannot be switched at will, and the presentation effect cannot meet the actual business requirements; 2. The extension conditions are single, and the extension cannot be retrieved according to the attribute conditions; 3. When the dynamic layout of the force-directed graph exceeds thousands of points, it is easy to freeze, and only one of the dynamic and static display effects of the force-directed graph is supported. Based on the visualization display level, the current knowledge graph display method cannot meet the requirements of users.

[0035] The present application provides a knowledge graph display method. In this embodiment, the point edge information to be rendered of the knowledge graph to be displayed is obtained; in response to the determination instruction of the target layout type, the graph of the point edge information to be rendered is generated according to the target layout type and the point edge information to be rendered; wherein the target layout type is one of the preset multiple layout types; the rendering type is determined according to the number of points and edges of the point edge to be rendered; according to the rendering type, the graph of the point edge information to be rendered is rendered to obtain a knowledge graph interface; and the knowledge graph interface is displayed. It can be seen that the present application provides a variety of preset layout types, and the user can flexibly select and switch according to the data structure, which can enrich the user's usage scenario; the present application can determine the rendering type of the knowledge graph according to the number of points and edges of the point edge information to be rendered, so as to ensure that the knowledge graph interface can accommodate more nodes and edges, so that the user can intuitively obtain more available information on the graph. It should be noted that the embodiments of the present application can be applied to electronic devices (such as mobile phones, tablets, computers, etc.) or servers. It should be noted that in addition to the above-mentioned methods, other implementation methods can also be used, which are not limited here.

[0036] Various non-limiting implementations of the present application are described in detail below in conjunction with the accompanying drawings.

[0037] See also Figure 1 , shows a knowledge graph display method in an embodiment of the present application. In this embodiment, the method may include the following steps:

[0038] S101: Obtain the vertex and edge information to be rendered of the knowledge graph to be displayed.

[0039] In this embodiment, when an instruction to display the knowledge graph to be displayed is received, it is necessary to obtain the edge information of the points to be rendered of the knowledge graph to be displayed. The edge information of the points to be rendered may include the ID, name, associated attributes, associated direction, number of associations and other attribute information of each entity object that needs to be displayed in the initial interface of the knowledge graph to be displayed. Each entity object may be provided with a corresponding node (i.e., point), and the points corresponding to the entity objects with a direct association relationship (i.e., a first-degree relationship) are connected by an edge.

[0040] S102: In response to a target layout type determination instruction, generating a graph of the point edge information to be rendered according to the target layout type and the point edge information to be rendered.

[0041] Among them, the target layout type is one of the preset multiple layout types. It should be noted that, in this embodiment, the preset multiple layout types may include a hierarchical layout type, a ring layout type, and a force-directed graph layout type. Specifically, in this embodiment, the front-end framework can be built based on vue, and multiple layouts can be implemented using cytoscape, canvas, and sankey built-in to solve the problem of single layout; for example, the implementation method of the hierarchical layout type can be: switch the json structure of the knowledge graph to be displayed to the json structure required by sankey, and draw the corresponding circular nodes and lines through the layer function to obtain the graphics of the point edge information to be rendered; the implementation method of the ring layout type can be: switch the json structure of the knowledge graph to be displayed to a grouped display structure with children as the hierarchy, and then draw it through canvas, so as to obtain the graphics of the point edge information to be rendered; the implementation method of the force-directed graph layout type can be: introduce cytoscape, and calculate the hierarchy of the graphics through the graphics drawing algorithm in the js through the structure of the graphics itself (such as the topological relationship between vertices and edges), so as to obtain the graphics of the point edge information to be rendered.

[0042] It should be noted that, when it is detected that the user has selected a target layout type, or at least one target layout type of the knowledge graph to be displayed is preset, or the target layout type is determined in real time according to the association relationship between each entity object in the knowledge graph to be displayed, a target layout type determination instruction can be generated. It is understandable that in one implementation, the target layout type determination instruction can include the target layout type, so that in response to the target layout type determination instruction, the graphics of the point edge information to be rendered can be generated according to the target layout type and the point edge information to be rendered.

[0043] In an implementation of this embodiment, the target layout type includes a node layout type and an interface layout type. The specific implementation of the step of generating a graph of the point edge information to be rendered according to the target layout type and the point edge information to be rendered in response to the target layout type determination instruction may be:

[0044] In response to the target layout type determination instruction, determining the interface position of each point and each edge corresponding to the point edge information to be rendered according to the interface layout type;

[0045] According to the node layout type, determine the style type of each point;

[0046] The graphics of the point edge information to be rendered are generated according to the interface positions of each point and each edge corresponding to the point edge information to be rendered, and the style type of each point.

[0047] In this embodiment, the target layout type determination instruction can be responded to first, and the interface positions of each point and each edge corresponding to the point edge information to be rendered can be determined according to the interface layout type. That is to say, the connection relationship between each point and each edge can be determined first according to the interface layout type and the association relationship between the entity objects of each point, and then the interface positions of each point and each edge in the interface can be determined.

[0048] In this embodiment, a Figure 2 The layout type and the hierarchical layout type selection interface are displayed. When the user determines the hierarchical layout type, the node layout type can be determined according to the hierarchical layout type. Then, the style type of each point (i.e., node) can be determined according to the node layout type, i.e., the display style of the point in the knowledge graph interface. Then, the graphics of the point edge information to be rendered can be generated according to the interface positions of each point and each edge corresponding to the point edge information to be rendered, as well as the style type of each point.

[0049] S103: Determine a rendering type according to the number of the point edges to be rendered.

[0050] In order to solve the problem of the single display effect of the knowledge graph, the present embodiment can support the switching between dynamic and static layout display effects. In the present embodiment, the rendering type can be determined according to the number of points and edges to be rendered (i.e., the number of points and edges to be rendered in the visualization area of ​​the knowledge graph). Specifically, if the number of points and edges to be rendered is less than a first preset threshold (such as 1000 points), the rendering type is determined to be static rendering; if the number of points and edges to be rendered is greater than the first preset threshold and less than the second preset threshold (such as 10000 points), the rendering type is determined to be dynamic rendering.

[0051] S104: Rendering the graphics of the point-edge information to be rendered according to the rendering type to obtain a knowledge graph interface.

[0052] In this embodiment, if the rendering type is static rendering, and the graphics of the point and edge information to be rendered are in a static state, after detecting the first preset operation (such as a single click) on the target entity object, the attribute information of the target entity object (such as the name of the target entity object) can be obtained, and the attribute information of the target entity object can be added at the position of the node corresponding to the target entity object. In this embodiment, each time the point and edge data in the visualization area changes, a DOM correction can be performed (i.e., the layout of the drawing is partially corrected, and when the data changes, the points and edges in the canvas are also increased or decreased accordingly), and the nodes and lines are displayed at the same time; multiple threads are opened according to the positions of each node in the canvas, and then the corresponding layout algorithm is called according to the layout type determined by the user or the system to calculate the positions of the new points and edges.

[0053] If the rendering type is dynamic rendering, and a lock operation is detected for the target entity object, the position of the target entity object and the entity objects related to the target entity object are fixed. For example, after the dynamic layout of the drawing is completed, drag a point in it, and other points will move and rearrange due to the force-directed repulsive force. At this time, right-click an entity and click Lock. Then, when dragging, the points related to the point will not move. For example: Assume that there are 6 points A, B, C, D, E, F, and G in the canvas of the knowledge graph, among which the points related to A are B, C, D, and E, and the points related to E are F and G. In the dynamic rendering layout, drag point E, by default, all points A, B, C, D, E, F, and G will recalculate their positions, and the positions of points and edges will change. If you click Lock A and then drag point E, the edge between A and E will move, and the four points A, B, C, and D will remain in their original positions. The edge between the four points A, B, C, and D will not move, and the positions of the points and edges of F and G will move.

[0054] When static rendering switches to dynamic rendering: click the dynamic button on the menu toolbar. If the number of points in the visualization area is less than the first preset threshold, it will switch directly to the dynamic layout. If it is greater than the first preset threshold, 1,000 points will be displayed in the visualization area by default, and the remaining points will be rendered in sequence by panning the canvas. When the dynamic layout switches to the static layout: click the static button on the menu toolbar to switch directly to the static layout. A pop-up window will pop up to prompt that the switch is successful. When adding or deleting nodes, the corresponding edges will be added when adding points, and the corresponding edges will be reduced when deleting points. The positions of other nodes will not change. In this way, the dynamic and static layouts will switch naturally after the drawing is translated and loaded, making the operation more convenient and practical.

[0055] That is to say, in this embodiment, the dynamic layout force-directed only displays relevant information of the point before it is static, and the associated edges are not rendered. The associated edges are rendered after the canvas is static, and clicking on an entity requests the background to display other properties of the entity. In this way, more points are rendered at one time and the dynamic effect will be smoother.

[0056] In order to solve the problem that the dynamic layout of the force-directed graph is prone to jamming or crashing when there are more than thousands of points, in one implementation of this embodiment, the attribute optimization of the point can be performed, that is, the graph database (such as the janusgraph graph database) only stores the basic attributes of the points and edges (such as id, name, and associated attributes), and the search server ES stores the full attributes of each point and edge. In the process of displaying the knowledge graph, when requesting the background graph database data, it is only necessary to return the id, name, and associated attributes of the points and edges. After the canvas is stationary and clicks on an entity object, it requests the background to display other attributes of the entity object, so that the surface can render more points at one time. It should be noted that since the data carried at one time during the canvas calculation cannot be too much, if the data attributes are all brought in by default, if a point has more than 20 attributes, the canvas will crash at about 500 points, so only the key attributes are brought in during the calculation, so that about 3000 points can be calculated. Therefore, clicking on an entity object to display the attribute information of the entity object can render multiple points and edges at one time. In addition, if the position of a point on the knowledge graph is not fixed or a point is dragged, the edges associated with the point will not be rendered, which can avoid the page crash when the canvas renders points and edges at the same time. In this way, the display effect of the force-directed graph can be optimized, and the graph can accommodate more nodes and edges, allowing users to intuitively obtain more available information on the graph.

[0057] S105: Displaying the knowledge graph interface.

[0058] After the knowledge graph interface is generated, the knowledge graph interface can be displayed.

[0059] It can be seen from the above technical solution that the present application provides a method for displaying a knowledge graph, the method comprising: obtaining the point and edge information to be rendered of the knowledge graph to be displayed; in response to the determination instruction of the target layout type, generating a graph of the point and edge information to be rendered according to the target layout type and the point and edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types; determining the rendering type according to the number of points and edges of the point and edge to be rendered; rendering the graph of the point and edge information to be rendered according to the rendering type to obtain a knowledge graph interface; and displaying the knowledge graph interface. It can be seen that the present application provides a plurality of preset layout types, and users can flexibly select and switch according to the data structure, which can enrich the user's usage scenarios; the present application can determine the rendering type of the knowledge graph according to the number of points and edges of the point and edge information to be rendered, so as to ensure that the knowledge graph interface can accommodate more nodes and edges, so that users can intuitively obtain more available information on the graph.

[0060] In order to solve the problem of single expansion condition in the existing knowledge graph display, in an implementation of this embodiment, the method further includes:

[0061] Step a: In response to an extension instruction for a target entity object, determining an extension type of the extension instruction.

[0062] If an expansion operation is detected in the knowledge graph interface for a target entity object (such as right-clicking the target entity object), an expansion instruction for the target entity object may be generated, wherein the expansion instruction includes an expansion type. In one implementation, the expansion type may include a shortcut association and a conditional association. Figure 3 As shown, right-click a single entity object in the knowledge graph interface or right-select multiple entities, and you can choose the expansion type as quick association or conditional association.

[0063] Step b: Determine the extended entity object of the target entity object according to the extended type.

[0064] Specifically, if the extension type is a shortcut association, the entity object that is in a first-degree relationship with the target entity object is used as the extended entity object of the target entity object. A first-degree relationship can be understood as a direct association relationship with the target entity object. The association relationship extended from an entity object with a direct association relationship is called a second-degree relationship, and so on. Figure 4 As shown in the figure, if the extension type is quick extension, all the relationships of the currently selected entity can be listed in the interface. After selecting the target relationship, click OK, and the request is transmitted to the server, and the server returns the nodes of the default first-degree relationships of these entities.

[0065] If the extension type is conditional association, then according to the attribute screening condition in the extension instruction, determine the entity object that meets the attribute screening condition among the entity objects that have an association relationship with the target entity object; and use the entity object that meets the attribute screening condition as the extended entity object of the target entity object. In one implementation, the attribute screening condition may include screening conditions such as the associated entity object, the associated attribute, the associated direction, and the number of associated times. Figure 5 , Figure 6 As shown in the figure, if the extension type is conditional association, right-click a single entity on the drawing or right-click multiple entities and select conditional extension. An entity association selection box will pop up. Select several edges, set the number and direction of relationships in turn, set the basic attribute filtering conditions of the edges, and then send the request to the server. The server returns the points and edges of the entity after conditional extension.

[0066] Step c: Display the extended entity object in the knowledge graph interface.

[0067] It can be seen that the implementation method of this embodiment can provide a variety of condition screening methods, enriching user query scenarios.

[0068] like Figure 7 As shown, it is a specific embodiment of a knowledge graph display device described in this application. The device described in this embodiment is a physical device for executing the method described in the above embodiment. Its technical solution is essentially consistent with the above embodiment. The device described in this embodiment includes:

[0069] The acquisition unit 701 is used to obtain the vertex edge information to be rendered of the knowledge graph to be displayed;

[0070] A response unit 702 is used to respond to a target layout type determination instruction and generate a graphic of the point edge information to be rendered according to the target layout type and the point edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types;

[0071] A determining unit 703, configured to determine a rendering type according to the number of point edges to be rendered;

[0072] A rendering unit 704 is used to render the graph of the point-edge information to be rendered according to the rendering type to obtain a knowledge graph interface;

[0073] The display unit 705 is used to display the knowledge graph interface.

[0074] Optionally, the target layout type includes a node layout type and an interface layout type; the response unit 702 is specifically used to:

[0075] In response to the target layout type determination instruction, determining the interface position of each point and each edge corresponding to the point edge information to be rendered according to the interface layout type;

[0076] According to the node layout type, determine the style type of each point;

[0077] The graphics of the point edge information to be rendered are generated according to the interface positions of each point and each edge corresponding to the point edge information to be rendered, and the style type of each point.

[0078] Optionally, the determining unit 703 is specifically configured to:

[0079] If the number of the edge points to be rendered is less than a first preset threshold, determining the rendering type to be static rendering;

[0080] If the number of the point edges to be rendered is greater than the first preset threshold and less than the second preset threshold, determining that the rendering type is dynamic rendering;

[0081] Accordingly, the rendering unit 704 is specifically configured to:

[0082] If the rendering type is static rendering, and the graph of the point edge information to be rendered is in a static state, a first preset operation for a target entity object is detected, attribute information of the target entity object is obtained, and the attribute information of the target entity object is added at a position of a node corresponding to the target entity object;

[0083] If the rendering type is dynamic rendering and a locking operation on a target entity object is detected, the positions of the target entity object and entity objects related to the target entity object are fixed.

[0084] Optionally, the device further includes an expansion unit, and the expansion unit is used to:

[0085] In response to an extension instruction for a target entity object, determining an extension type of the extension instruction;

[0086] Determining an extended entity object of the target entity object according to the extension type;

[0087] In the knowledge graph interface, the extended entity object is displayed.

[0088] Optionally, the expansion unit is specifically used for:

[0089] If the extension type is a quick association, an entity object having a first-degree relationship with the target entity object is used as an extended entity object of the target entity object;

[0090] If the extension type is conditional association, then according to the attribute screening condition in the extension instruction, an entity object that meets the attribute screening condition is determined among the entity objects associated with the target entity object; and the entity object that meets the attribute screening condition is used as an extended entity object of the target entity object.

[0091] like Figure 8As shown, it is a specific embodiment of a knowledge graph display system described in the present application. The knowledge graph display system includes: a task scheduler (i.e., a worker scheduler), a graph resource pool, a knowledge graph display platform, a knowledge database (i.e., knowledge storage), and an interface layer (i.e., a cytoscape container). Among them, the knowledge database stores the knowledge data to be displayed in the knowledge graph. It can be understood that the knowledge database is used to store knowledge and can be provided to the data source of the knowledge relationship displayed by the front end; the interface layer encapsulates a number of interfaces for accessing the knowledge database. In one implementation, the interface layer can encapsulate the cytoscape API as a link from the back-end storage to the front-end display. The knowledge graph display platform may include a rendering engine, a layout container, and an extended filter; the layout container can be used to display the layout supported by the current knowledge graph, and can provide a knowledge graph layout switching function; the rendering engine can be used to provide force-directed and static point-edge rendering methods, and can also support manual local switching of the point-edge rendering method of the drawing, and can also automatically switch the rendering method according to the overall data volume; the extended filter can be used to expand the point edges of the drawing according to attributes or relationships. The task scheduler can be understood as a surface data calculation engine. It can take out the layouter supported by the current knowledge graph (i.e., the knowledge graph to be displayed) and store all the calculated results required for the layout into the graph resource pool. It can be understood that the task scheduler is specifically used to monitor the user's operations and switching instructions in the canvas, call the corresponding layout algorithm to calculate the positions of points and edges, and then store the results in the resource pool.

[0092] The task scheduler is used to obtain the point edge information to be rendered of the knowledge graph to be displayed in the knowledge database through the interface layer; in response to the instruction to determine the target layout type, generate a graph of the point edge information to be rendered according to the target layout type and the point edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types; and store the graph of the point edge information to be rendered in the graph resource pool. In one implementation, the task scheduler is specifically used to: if the number of point edges of the point edges to be rendered is less than a first preset threshold, determine that the rendering type is static rendering; if the number of point edges of the point edges to be rendered is greater than the first preset threshold and less than a second preset threshold, determine that the rendering type is dynamic rendering.

[0093] In this embodiment, when the task scheduler receives an instruction to display the knowledge graph to be displayed, the task scheduler needs to obtain the edge information of the points to be rendered of the knowledge graph to be displayed in the knowledge database through the interface layer. The edge information of the points to be rendered may include the ID, name, associated attributes, associated direction, number of associations and other attribute information of each entity object that needs to be displayed in the initial interface of the knowledge graph to be displayed. Each entity object may be provided with a corresponding node (i.e., point), and the points corresponding to the entity objects with a direct association relationship (i.e., a first-degree relationship) are connected by an edge.

[0094] Among them, the target layout type is one of the preset multiple layout types. It should be noted that in this embodiment, multiple layout types are preset in the knowledge database, such as hierarchical layout type, ring layout type, and force-directed graph layout type. Specifically, in this embodiment, the task scheduler can build a front-end framework based on vue, and use cytoscape, canvas and sankey to implement multiple layouts to solve the problem of single layout; for example, the implementation method of the hierarchical layout type can be: the task scheduler switches the json structure of the knowledge graph to be displayed to the json structure required by sankey, and draws the corresponding circular nodes and lines through the layer function, so as to obtain the graphics of the point edge information to be rendered; the implementation method of the ring layout type can be: the task scheduler switches the json structure of the knowledge graph to be displayed to a grouped display structure with children as the hierarchy, and then draws it through canvas, so as to obtain the graphics of the point edge information to be rendered; the implementation method of the force-directed graph layout type can be: the task scheduler introduces cytoscape, and calculates the hierarchy of the graphics through the graphics drawing algorithm in the js through the structure of the graphics itself (such as the topological relationship between vertices and edges), so as to obtain the graphics of the point edge information to be rendered.

[0095] It should be noted that, when the task scheduler detects that the user has selected a target layout type, or presets at least one target layout type of the knowledge graph to be displayed, or determines the target layout type in real time based on the association relationship between the entity objects in the knowledge graph to be displayed, the task scheduler can generate a target layout type determination instruction. It is understandable that, in one implementation, the target layout type determination instruction can include the target layout type, so that the task scheduler can respond to the target layout type determination instruction and generate the graphics of the point edge information to be rendered according to the target layout type and the point edge information to be rendered.

[0096] In an implementation of this embodiment, the target layout type includes a node layout type and an interface layout type. The task scheduler responds to the target layout type determination instruction, and generates the graphics of the point edge information to be rendered according to the target layout type and the point edge information to be rendered. The specific implementation method may be:

[0097] The task scheduler responds to the target layout type determination instruction and determines the interface position of each point and each edge corresponding to the point edge information to be rendered according to the interface layout type;

[0098] The task scheduler determines the style type of each point based on the node layout type;

[0099] The task scheduler generates a graphic of the point edge information to be rendered according to the interface positions of each point and each edge corresponding to the point edge information to be rendered, and the style type of each point.

[0100] In this embodiment, the task scheduler can first respond to the determination instruction of the target layout type, and determine the interface position of each point and each edge corresponding to the point edge information to be rendered according to the interface layout type. In other words, the connection relationship between each point and each edge can be determined based on the interface layout type and the association relationship between the entity objects of each point, and then the interface position of each point and each edge in the interface can be determined.

[0101] In this embodiment, a Figure 2 The task scheduler detects the user's determination of the hierarchical layout type and the selection interface of the hierarchical layout type. It can determine the node layout type according to the hierarchical layout type, and then determine the style type of each point (i.e., node) according to the node layout type, that is, the display style of the point in the knowledge graph interface. Then, the graphics of the point edge information to be rendered can be generated according to the interface positions of each point and each edge corresponding to the point edge information to be rendered, as well as the style type of each point. The task scheduler stores the graphics of the point edge information to be rendered in the graph resource pool.

[0102] The knowledge graph display platform is used to read the graphics of the point-edge information to be rendered in the graph resource pool; determine the rendering type according to the number of points and edges to be rendered; render the graphics of the point-edge information to be rendered according to the rendering type to obtain a knowledge graph interface; and display the knowledge graph interface.

[0103] In one implementation, the target layout type includes a node layout type and an interface layout type.

[0104] The layout container can be used to obtain the layout types supported by the knowledge graph to be displayed from the graph resource pool, and display the layout types supported by the knowledge graph to be displayed, so that the user can select the layout type of the knowledge graph to be displayed.

[0105] The rendering engine can be used to respond to a determination instruction of a target layout type, determine the interface position of each point and each edge corresponding to the point edge information to be rendered according to the interface layout type; determine the style type of each point according to the node layout type; and generate a graphic of the point edge information to be rendered according to the interface position of each point and each edge corresponding to the point edge information to be rendered, and the style type of each point.

[0106] The rendering engine is specifically used for:

[0107] If the rendering type is static rendering, and the graph of the point edge information to be rendered is in a static state, a first preset operation for a target entity object is detected, attribute information of the target entity object is obtained, and the attribute information of the target entity object is added at a position of a node corresponding to the target entity object;

[0108] If the rendering type is dynamic rendering and a locking operation on a target entity object is detected, the positions of the target entity object and entity objects related to the target entity object are fixed.

[0109] In order to solve the problem of the single graphic display effect of the knowledge graph, the rendering engine in this embodiment can support the switching of dynamic and static layout display effects. In this embodiment, the rendering engine can determine the rendering type according to the number of points and edges to be rendered (that is, the number of points and edges to be rendered in the visualization area of ​​the knowledge graph). Specifically, if the number of points and edges to be rendered is less than a first preset threshold (such as 1000 points), the rendering engine determines the rendering type as static rendering; if the number of points and edges to be rendered is greater than the first preset threshold and less than the second preset threshold (such as 10,000 points), the rendering engine determines the rendering type as dynamic rendering.

[0110] In this embodiment, if the rendering type is static rendering, and the graphics of the point and edge information to be rendered are in a static state, after the rendering engine detects the first preset operation (such as a single click) on the target entity object, it can obtain the attribute information of the target entity object (such as the name of the target entity object), and add the attribute information of the target entity object at the position of the node corresponding to the target entity object. In this embodiment, each time the point and edge data in the visualization area changes, the rendering engine can perform DOM correction (i.e., the layout of the drawing is partially corrected, and when the data changes, the points and edges in the canvas are also increased or decreased accordingly), and display the nodes and lines at the same time; the rendering engine can start multiple threads based on the positions of each node in the canvas, and then the rendering engine calls the corresponding layout algorithm according to the layout type determined by the user or the system to calculate the positions of the new points and edges.

[0111] If the rendering type is dynamic rendering, and the rendering engine detects a locking operation for the target entity object, the rendering engine fixes the position of the target entity object and the entity objects related to the target entity object. For example, after the dynamic layout of the drawing is completed, drag a point in it, and other points will move and rearrange due to the force-directed repulsive force. At this time, right-click an entity and click Lock. Then, when dragging, the points related to the point will not move. For example: Assume that there are 6 points A, B, C, D, E, F, and G in the canvas of the knowledge graph, among which the points related to A are B, C, D, and E, and the points related to E are F and G. Under the dynamic rendering layout, drag point E, by default, all points A, B, C, D, E, F, and G will recalculate their positions, and the positions of points and edges will change. If you click Lock A and then drag point E, the edge between A and E will move, and the 4 points A, B, C, and D will remain in their original positions. The edge between the 4 points A, B, C, and D will not move, and the positions of the points and edges of F and G will move.

[0112] The case where static rendering switches to dynamic rendering: If it is detected that the user clicks the dynamic button on the menu toolbar, and if the points in the visualization area are less than the first preset threshold, the rendering engine directly switches to the dynamic layout. If it is greater than the first preset threshold, the rendering engine will take 1,000 points by default to display in the visualization area, and render the remaining points in sequence by panning the canvas. The case where the dynamic layout switches to the static layout: If it is detected that the user clicks the static button on the menu toolbar, the rendering engine directly switches to the static layout, and a pop-up box prompts that the switch is successful. When adding or deleting nodes, the corresponding edges will be added when adding points, and the corresponding edges will be reduced when deleting points. The positions of other nodes will not change. In this way, the dynamic and static layouts are naturally switched after the drawing is translated and loaded, making the operation more convenient and practical.

[0113] That is to say, in this embodiment, before the dynamic layout force is static, the rendering engine only displays the relevant information of the point, and the associated edges are not rendered. The associated edges are rendered after the canvas is static, and clicking on an entity will request the background to display other properties of the entity. In this way, more points can be rendered at one time and the dynamic effect will be smoother.

[0114] In order to solve the problem that the dynamic layout of the force-directed graph is prone to jamming or crashing when there are more than thousands of points, in one implementation of this embodiment, the rendering engine can optimize the attributes of the points, that is, the graph database (such as the janusgraph graph database) only stores the basic attributes of the points and edges (such as id, name, and associated attributes), while the search server ES stores the full attributes of each point and edge. In the process of displaying the knowledge graph, when requesting the background graph database data, the rendering engine only needs to return the id, name, and associated attributes of the points and edges. After the canvas is stationary and a certain entity object is clicked, the rendering engine requests the background to display other attributes of the entity object, so that the drawing can render more points at one time. It should be noted that since the data carried at one time during the canvas calculation cannot be too much, if the data attributes are all brought in by default, if a point has more than 20 attributes, the canvas will crash at about 500 points, so only the key attributes are brought in during the calculation, so that about 3000 points can be calculated. Therefore, clicking an entity object to display the attribute information of the entity object can render multiple points and edges at one time. In addition, if the position of a point on the knowledge graph is not fixed or a point is dragged, the edges associated with the point will not be rendered, which can avoid the page crash when the canvas renders points and edges at the same time. In this way, the display effect of the force-directed graph can be optimized, and the graph can accommodate more nodes and edges, allowing users to intuitively obtain more available information on the graph. After the rendering engine generates the knowledge graph interface, the knowledge graph interface can be displayed.

[0115] It can be seen from the above technical scheme that the present application provides a knowledge graph display system, which includes: a task scheduler, a graph resource pool, a knowledge graph display platform, a knowledge database and an interface layer; wherein the knowledge database stores knowledge data of the knowledge graph to be displayed; the interface layer encapsulates a number of interfaces for accessing the knowledge database; the task scheduler is used to obtain the point edge information to be rendered of the knowledge graph to be displayed in the knowledge database through the interface layer; in response to the target layout type determination instruction, generate a graphic of the point edge information to be rendered according to the target layout type and the point edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types; and, store the graphic of the point edge information to be rendered in the graph resource pool; the knowledge graph display platform is used to read the graphic of the point edge information to be rendered in the graph resource pool; determine the rendering type according to the number of points and edges of the points and edges to be rendered; render the graphic of the point edge information to be rendered according to the rendering type to obtain a knowledge graph interface; and display the knowledge graph interface. It can be seen that the present application provides a variety of preset layout types, and users can flexibly select and switch according to the data structure, which can enrich the user usage scenarios; the present application can determine the rendering type of the knowledge graph according to the number of points and edges to be rendered, so as to ensure that the knowledge graph interface can accommodate more nodes and edges, so that users can intuitively obtain more available information on the graph.

[0116] In order to solve the problem of single extension condition in the existing knowledge graph display, in one implementation of this embodiment, the knowledge graph display platform also includes an extension filter.

[0117] The extension filter is used to determine the extension type of an extension instruction in response to an extension instruction for a target entity object; determine the extended entity object of the target entity object according to the extension type; and display the extended entity object in the knowledge graph interface.

[0118] As an example, the extended filter is specifically used for:

[0119] If the extension type is a quick association, an entity object having a first-degree relationship with the target entity object is used as an extended entity object of the target entity object;

[0120] If the extension type is conditional association, then according to the attribute screening condition in the extension instruction, an entity object that meets the attribute screening condition is determined among the entity objects associated with the target entity object; and the entity object that meets the attribute screening condition is used as an extended entity object of the target entity object.

[0121] If the extension filter detects that an extension operation is performed on a target entity object in the knowledge graph interface (such as right-clicking the target entity object), the extension filter can generate an extension instruction for the target entity object, wherein the extension instruction includes an extension type. In one implementation, the extension type can include a shortcut association and a conditional association. Figure 3 As shown, it is detected that the user right-clicks a single entity object in the knowledge graph interface or right-clicks multiple entities, and the extended filter can select the extension type as quick association or conditional association.

[0122] Specifically, if the extension type is a quick association, the extension filter may use the entity object that has a first-degree relationship with the target entity object as the extended entity object of the target entity object. A first-degree relationship can be understood as a direct association relationship with the target entity object. The association relationship extended from an entity object with a direct association relationship is called a second-degree relationship, and so on. Figure 4 As shown, if the extension type is quick extension, the extension filter can list all the relationships of the currently selected entity in the sub-ah interface. After selecting the target relationship, click OK, and the request is transmitted to the server. The server returns the nodes of the default first-degree relationships of these entities.

[0123] If the extension type is conditional association, the extension filter can determine the entity objects that meet the attribute screening conditions among the entity objects that have an association relationship with the target entity object according to the attribute screening conditions in the extension instruction; the extension filter can use the entity objects that meet the attribute screening conditions as the extended entity objects of the target entity object. In one implementation, the attribute screening conditions may include screening conditions such as associated entity objects, associated attributes, associated directions, and the number of associated times. Figure 5 , Figure 6 As shown in the figure, if the extension type is conditional association, the extension filter can right-click a single entity on the drawing or right-click multiple entities to select conditional extension, and an entity association selection box will pop up. Select several edges, set the number and direction of relationships in turn, set the basic attribute filtering conditions of the edges, and then send the request to the server. The server returns the points and edges of the entity after conditional extension.

[0124] It can be seen that the implementation method of the extended filter in this embodiment can provide multiple conditional filtering methods, enriching the user query scenarios.

[0125] Fig. 9It is a structural diagram of an electronic device provided in an embodiment of the present application. At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. Among them, the memory may include a memory, such as a high-speed random access memory (Random-Access Memory, RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage, etc. Of course, the electronic device may also include hardware required for other services.

[0126] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0127] The memory is used to store execution instructions. Specifically, the execution instructions are computer programs that can be executed. The memory may include internal memory and non-volatile memory, and provides execution instructions and data to the processor.

[0128] In one possible implementation, the processor reads the corresponding execution instructions from the non-volatile memory into the memory and then runs them, and can also obtain the corresponding execution instructions from other devices to form a knowledge graph display device at the logical level. The processor executes the execution instructions stored in the memory to implement the knowledge graph display method provided in any embodiment of the present application through the executed execution instructions.

[0129] The above application Figure 1The method performed by the knowledge graph display device provided in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0130] The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0131] An embodiment of the present application also proposes a readable storage medium, which stores execution instructions. When the stored execution instructions are executed by a processor of an electronic device, the electronic device can execute the knowledge graph display method provided in any embodiment of the present application, and is specifically used to execute the method described above for knowledge graph display.

[0132] The electronic device described in the above embodiments may be a computer.

[0133] Those skilled in the art should understand that the embodiments of the present application can be provided as methods or computer program products. Therefore, the present application can adopt a complete hardware embodiment, a complete software embodiment, or a combination of software and hardware.

[0134] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0135] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0136] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A knowledge graph display method, characterized in that: The method comprises: Get the vertex and edge information to be rendered of the knowledge graph to be displayed; In response to a target layout type determination instruction, a graph of the point edge information to be rendered is generated according to the target layout type and the point edge information to be rendered; wherein the target layout type is one of a plurality of preset layout types, and the target layout type includes a node layout type and an interface layout type; Determining a rendering type according to the number of the points and edges to be rendered; Rendering the graph of the point-edge information to be rendered according to the rendering type to obtain a knowledge graph interface; Displaying the knowledge graph interface; The step of generating a graph of the point edge information to be rendered in response to a target layout type determination instruction and according to the target layout type and the point edge information to be rendered comprises: In response to the target layout type determination instruction, determining the interface position of each point and each edge corresponding to the point edge information to be rendered according to the interface layout type; According to the node layout type, determine the style type of each point; The graphics of the point edge information to be rendered are generated according to the interface positions of each point and each edge corresponding to the point edge information to be rendered, and the style type of each point.

2. The method according to claim 1, characterized in that The number of points and edges to be rendered and the type of rendering are determined, including: If the number of the edge points to be rendered is less than a first preset threshold, determining the rendering type to be static rendering; If the number of the point edges to be rendered is greater than the first preset threshold and less than the second preset threshold, determining that the rendering type is dynamic rendering; Correspondingly, the graphics of the point-edge information to be rendered are rendered according to the rendering type to obtain a knowledge graph interface, including: If the rendering type is static rendering, and the graph of the point edge information to be rendered is in a static state, a first preset operation for a target entity object is detected, attribute information of the target entity object is obtained, and the attribute information of the target entity object is added at a position of a node corresponding to the target entity object; If the rendering type is dynamic rendering and a locking operation on a target entity object is detected, the positions of the target entity object and entity objects related to the target entity object are fixed.

3. The method according to any one of claims 1-2, characterized in that: The method further comprises: In response to an extension instruction for a target entity object, determining an extension type of the extension instruction; Determining an extended entity object of the target entity object according to the extension type; In the knowledge graph interface, the extended entity object is displayed.

4. The method according to claim 3, characterized in that The step of determining the extended entity object of the target entity object according to the extended type includes: If the extension type is a quick association, an entity object having a first-degree relationship with the target entity object is used as an extended entity object of the target entity object; If the extension type is conditional association, then according to the attribute screening condition in the extension instruction, an entity object that meets the attribute screening condition is determined among the entity objects associated with the target entity object; and the entity object that meets the attribute screening condition is used as an extended entity object of the target entity object.

5. A knowledge graph display system, characterized in that: The system includes: a task scheduler, a graph resource pool, a knowledge graph display platform, a knowledge database and an interface layer; wherein the knowledge database stores knowledge data to be displayed in the knowledge graph; the interface layer encapsulates a number of interfaces for accessing the knowledge database; The task scheduler is used to obtain the to-be-rendered point edge information of the to-be-rendered knowledge graph in the knowledge database through the interface layer; in response to a determination instruction of a target layout type, generate a graph of the to-be-rendered point edge information according to the target layout type and the to-be-rendered point edge information; wherein the target layout type is one of a plurality of preset layout types, and the target layout type includes a node layout type and an interface layout type; and store the graph of the to-be-rendered point edge information in the graph resource pool; The knowledge graph display platform is used to read the graph of the point-edge information to be rendered in the graph resource pool; determine the rendering type according to the number of points and edges to be rendered; render the graph of the point-edge information to be rendered according to the rendering type to obtain a knowledge graph interface; and display the knowledge graph interface; The step of generating a graph of the point edge information to be rendered in response to a target layout type determination instruction and according to the target layout type and the point edge information to be rendered comprises: In response to the target layout type determination instruction, determining the interface position of each point and each edge corresponding to the point edge information to be rendered according to the interface layout type; According to the node layout type, determine the style type of each point; The graphics of the point edge information to be rendered are generated according to the interface positions of each point and each edge corresponding to the point edge information to be rendered, and the style type of each point.

6. The system according to claim 5, characterized in that The knowledge graph display platform includes a rendering engine and a layout container; the target layout type includes a node layout type and an interface layout type; The layout container is used to obtain the layout types supported by the knowledge graph to be displayed from the graph resource pool, and to display the layout types supported by the knowledge graph to be displayed; The rendering engine is used to respond to the target layout type determination instruction, determine the interface position of each point and each edge corresponding to the point edge information to be rendered according to the interface layout type; determine the style type of each point according to the node layout type; generate the graphics of the point edge information to be rendered according to the interface position of each point and each edge corresponding to the point edge information to be rendered, and the style type of each point.

7. The system according to claim 6, characterized in that The task scheduler is specifically used for: If the number of the edge points to be rendered is less than a first preset threshold, determining the rendering type to be static rendering; If the number of the point edges to be rendered is greater than the first preset threshold and less than the second preset threshold, determining that the rendering type is dynamic rendering; Accordingly, the rendering engine is specifically used for: If the rendering type is static rendering, and the graph of the point edge information to be rendered is in a static state, a first preset operation for a target entity object is detected, attribute information of the target entity object is obtained, and the attribute information of the target entity object is added at a position of a node corresponding to the target entity object; If the rendering type is dynamic rendering and a locking operation on a target entity object is detected, the positions of the target entity object and entity objects related to the target entity object are fixed.

8. The system according to any one of claims 5 to 7, characterized in that: The knowledge graph display platform also includes an extended filter; The extension filter is used to determine the extension type of an extension instruction in response to an extension instruction for a target entity object; determine the extended entity object of the target entity object according to the extension type; and display the extended entity object in the knowledge graph interface.

9. The system according to claim 8, characterized in that The extended filter is specifically used for: If the extension type is a quick association, an entity object having a first-degree relationship with the target entity object is used as an extended entity object of the target entity object; If the extension type is conditional association, then according to the attribute screening condition in the extension instruction, an entity object that meets the attribute screening condition is determined among the entity objects associated with the target entity object; and the entity object that meets the attribute screening condition is used as an extended entity object of the target entity object.

Images