Method, apparatus, device and medium for managing knowledge base

Abstract

According to example embodiments of the present disclosure, a method, apparatus, device, and computer-readable storage medium for managing a knowledge base are provided. A method for managing a knowledge base includes: in response to receiving a request to modify a rule for a first namespace, copying the rule to the first namespace, the rule being used to constrain structured data in the knowledge base; modifying the rule in the first namespace based on the request to modify the rule; and adding the modified rule to a rule base associated with the knowledge base. Thus, this solution offers excellent reusability and traceability while flexibly adapting to the needs of different knowledge bases.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of information processing, and more particularly, to methods, apparatuses, devices, and computer-readable storage media for managing a knowledge base. Background Art

[0002] A knowledge base consists of a large amount of structured data. This structured data must adhere to certain representation specifications to make it readable by humans and understandable by machines. The representation specifications used to constrain structured data are called rules or schemas.

[0003] Typically, when there are numerous knowledge base instances (such as general knowledge bases, industry knowledge bases related to various professional fields, and application knowledge bases related to various products), descriptions of domain knowledge overlap between different knowledge bases. For example, both a film and television library and a celebrity library contain data on entertainment celebrities, so the rules defined for these knowledge bases also have significant similarities. However, traditional technologies cannot cost-effectively define rules for a large number of knowledge bases. Summary of the Invention

[0004] According to an example embodiment of the present disclosure, a solution for managing a knowledge base is provided.

[0005] In a first aspect of the present disclosure, a method for managing a knowledge base is provided, comprising: in response to receiving a request to modify a rule for a first namespace, causing the rule to be copied to the first namespace, the rule being used to constrain structured data in the knowledge base; based on the request to modify the rule, modifying the rule in the first namespace; and adding the modified rule to a rule base associated with the knowledge base.

[0006] In a second aspect of the present disclosure, a device for managing a knowledge base is provided, comprising: a copy module configured to, in response to receiving a request to modify a rule for a first namespace, copy the rule to the first namespace, the rule being used to constrain structured data in the knowledge base; a modification module configured to modify the rule in the first namespace based on the request to modify the rule; and an addition module configured to add the modified rule to a rule base associated with the knowledge base.

[0007] In a third aspect of the present disclosure, an electronic device is provided, comprising one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the method according to the first aspect of the present disclosure.

[0008] In a fourth aspect of the present disclosure, a computer-readable medium is provided, on which a computer program is stored. When the program is executed by a processor, the method according to the first aspect of the present disclosure is implemented.

[0009] It should be understood that the contents described in the Summary of the Invention section are not intended to limit the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0011] Figure 1 A schematic diagram illustrating an example environment in which embodiments of the present disclosure can be implemented;

[0012] Figure 2 A schematic diagram illustrating another example environment in which embodiments of the present disclosure can be implemented;

[0013] Figure 3 A flowchart for managing a knowledge base according to some embodiments of the present disclosure is shown;

[0014] Figure 4 A schematic block diagram illustrating an apparatus for managing a knowledge base according to some embodiments of the present disclosure; and

[0015] Figure 5 A block diagram of a computing device capable of implementing some embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0016] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0017] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to." The term "based on" should be understood as "based at least in part on." The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment." The terms "first," "second," etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0018] The term "knowledge base" refers to a graph-based data structure consisting of nodes and edges, such as a knowledge graph or other suitable database. In a knowledge base, each node represents an entity in the real world, and each edge represents a relationship between entities. A knowledge base is an effective representation of relationships. In other words, a knowledge base connects different types of information to form a relational network, thus providing the ability to analyze problems from a "relational" perspective. The term "rule" refers to the representation specifications used to constrain structured data in a knowledge base. The term "namespace" refers to a form of code organization. Namespaces are used to organize and reuse code and to distinguish different code functions.

[0019] As mentioned above, traditional technologies cannot cost-effectively define rules for a large number of knowledge bases. Traditionally, there are two approaches to cross-knowledge base rule definition. In the first approach, knowledge base owners are independently responsible for developing their own rules. In the case of knowledge bases with overlapping data, the established rule systems are shared offline.

[0020] While independently defined rules offer the advantages of efficiency and isolation, the management costs of the rule system, as well as the use and reuse costs of data, increase significantly when there are a large number of rules. For example, different owners may define different symbols for semantically identical classes or attributes. Conversely, different owners may assign completely different semantics to the same symbol. Furthermore, since duplication between different rule systems is impossible to trace, once-consistent symbols may become inconsistent after a period of upgrades. These issues lead to the need for extensive rule mapping and are prone to errors when performing knowledge association and calculations across knowledge bases.

[0021] In the second approach, a unified rule system is defined so that all knowledge bases adhere to its constraints. While maintaining a unified rule system can address the problem of knowledge representation consistency, it inevitably leads to other problems. For example, the cost of defining and merging rule systems is high, requiring significant expertise and time from those defining them. This results in a long update cycle for unified rule systems, hindering the rapid iteration of products. Furthermore, different application scenarios have varying degrees of reliance on knowledge base representation. Even for the same knowledge, different applications may require completely different knowledge representation specifications. A unified rule system cannot resolve these issues. Therefore, a solution for managing knowledge graphs is proposed.

[0022] In general, according to the embodiments of the present disclosure, when a rule customization requirement arises in a namespace, the rules can be copied (forked) from a rule base containing uniformly defined rules or another namespace into the namespace, and the copied rules can be modified to meet the customization requirements of different knowledge bases. Furthermore, the modified rules can be added / merged into the rule base to expand the rule base. As a result, this solution has good reusability and traceability while flexibly adapting to the needs of different knowledge bases.

[0023] Figure 1 1 is a schematic diagram illustrating an example environment 100 in which embodiments of the present disclosure can be implemented. Figure 1 As shown, environment 100 includes a computing device 110, a user 120 (also referred to as a "first user"), a namespace 130 for the first user (also referred to as a "first namespace"), and a rule base 140. For example, computing device 110 may be any device with computing capabilities, such as a distributed computing device, a mainframe, a server, a personal computer, a tablet computer, a smart phone, or the like.

[0024] As mentioned above, the knowledge base consists of a large amount of structured data. This structured data needs to follow certain representation specifications. The representation specifications used to constrain structured data are called rules. In some embodiments, structured data can be represented as triples. The following is a specific example of structured data and rules:

[0025] The first structured data: (Andy Lau, wife, Zhu Liqian),

[0026] Second structured data: (Andy Lau, isA, Person),

[0027] The third structured data: (Zhu Liqian, isA, Person),

[0028] Rules: (Person, wife, Person),

[0029] The first structured data, the second structured data, and the third structured data represented by triples represent objective facts or entities, and the rules are knowledge constraints based on objective facts or entity abstractions. The rules can be used to verify the legitimacy of the first structured data, the second structured data, and the third structured data, and can also be used to guide the production of similar knowledge. Rules can contain entities and relationships between entities. For example, the rule "(Person, wife, Person)" can contain the entity "Person" (also known as a class) and the relationship between the entity "wife" (also known as an attribute).

[0030] Rule library 140 may contain uniformly defined rules. In some embodiments, when creating a new knowledge base, first user 120 may request computing device 110 to directly reuse uniformly defined rules from rule library 140, such as the rule "(Person, wife, Person)." However, in some embodiments, uniformly defined rules may not meet the requirements of a particular knowledge base. For example, first user 120 may wish to use the more specific rule "(Male, wife, Female)."

[0031] Therefore, when a need arises to customize the knowledge base, the first user 120 may request the computing device 110 to modify the uniformly defined rules. The computing device 110 may cause the requested rules to be copied to the first namespace 130 and modify the copied rules. For example, the computing device 110 may cause the rule "(Person, wife, Person)" to be copied from the rule base 140 or a namespace for another user (also referred to as the "second user") (also referred to as the "second namespace") to the first namespace 130 and modify it to the rule "(Male, wife, Female)".

[0032] In some embodiments, the modified rules may be added to the rule base 140 to expand the rule base 140. For example, the first user 120 may request the computing device 110 to add the modified rules to the rule base 140. In this case, the reviewer will review the rules to be added and add the rules that meet the predetermined criteria to the rule base 140.

[0033] For example, the reviewer may determine that the rule “(Male, wife, Female)” meets predetermined criteria regarding the expression of the rule, thereby allowing the rule “(Male, wife, Female)” to be added to the rule base 140 to expand the rule base 140 .

[0034] On the contrary, the auditor may determine that the rule "(Nanren, wife, Nvren)" does not meet the predetermined standard for the expression of the rule (for example, the rule is not allowed to be expressed in Chinese pinyin), and thus the rule "(Nanren, wife, Nvren)" is not allowed to be added to the rule base 140. It should be understood that although the expression of the rule is used as an example of the predetermined standard, any appropriate restriction on the rule can be used as the predetermined standard. In addition, although it is described above that the auditor can review the rules, any appropriate subject can review the rules, for example, including but not limited to the first user 120 itself and users associated with other namespaces who will use the rule base (such as the second user).

[0035] Furthermore, in some embodiments, the computing device 110 records the actions of modifying the rules and adding the modified rules in the first namespace 130 , thereby supporting traceability and synchronization of the rules.

[0036] This satisfies the need for continuous expansion of the rule base containing standard rules, while enabling the rapid creation of customized rules to support rapid iteration of the knowledge base. Furthermore, through standard development mechanisms, dependencies between different versions of rules (e.g., original and modified rules) are preserved, and the act of adding rules is recorded, thus supporting rule traceability and synchronization.

[0037] Figure 2 A schematic diagram of another example environment 200 is shown in which embodiments of the present disclosure can be implemented. The environment 200 is Figure 1 The environment 100 is a specific implementation of the environment 100 in FIG. It should be understood that the environment 100 can also be implemented in any other appropriate form. The environment 200 includes an underlying architecture 210, a warehouse management system 220, and a rule platform 230.

[0038] The underlying architecture 210 includes a resource description framework 212 and a syntax definition module 214. The resource module framework 212 is a markup language for describing Web resources. The resource module framework 212 is used to process resource metadata and uses a "subject-verb-object" structure (or triple) of "resource-attribute-attribute-value" to describe metadata as a data model. For example, the resource module framework 212 can be W3C RDF / RDFS (World Wide Web Consortium, Resource Description Framework / Resource Description Framework Schema).

[0039] The grammar attribution module 214 can encapsulate the resource description framework 212 so that users do not need to know the specifications of the resource description framework 212. Therefore, the grammar attribution module 214 can provide the specifications for defining rules to support the description of rules. In some embodiments, the grammar attribution module 214 can support the definition of uniformly defined rules in the rule library 140 and can modify the rules.

[0040] The rule base 140 and namespaces (such as the first namespace 130, the second namespace 226, and the third namespace 228) can be hosted in a warehouse management system 220. In some embodiments, the warehouse management system 220 can perform version control, such as recording the actions of modifying rules and adding modified rules, thereby supporting rule traceability and synchronization. For example, the warehouse management system 220 can be GitLab.

[0041] As described above, when a new knowledge base is created, the first user 120 can request the computing device 110 to directly reuse the uniformly defined rules in the rule base 140. Alternatively, the first user 120 can also request the computing device 110 to reuse the rules in the second namespace 226.

[0042] When a uniformly defined rule or a rule copied from another namespace fails to meet the requirements of a specific knowledge base, first user 120 may request that computing device 110 modify the rule. Computing device 110 may copy the requested rule to first namespace 130 and modify the copied rule. For example, computing device 110 may copy the rule "(Person, wife, Person)" to first namespace 130 and modify it to the rule "(Male, wife, Female)."

[0043] In addition, if a user associated with the third namespace 228 (also referred to as a "third user") requests to use the rules in the first namespace 130, the rules in the first namespace 130 (e.g., the modified rules) may also be copied to the third namespace 228 for use or modification. Furthermore, if the first user 120 requests to add the modified rules to the rule base 140, the modified rules may be added to the rule base 140 after approval by the auditor, thereby expanding the rule base 140.

[0044] The rule platform 230 includes a visualization output module 232 and an application programming interface (API) output module 234. In some embodiments, after the rules in the namespace are registered with the rule platform 230, the visualization output module 232 can output the rules to the user through a visualization page, and the API output module 234 can also output the rules in response to a call to the rules.

[0045] As a result, semantically identical classes and attributes are largely retained as rules are modified based on the initial rules. Furthermore, since rule replication is maintained by the warehouse management system 220, upstream synchronization and downstream updates via rule addition requests are facilitated, ensuring rule consistency. Furthermore, updates to the rule base 140 no longer rely on the efficiency of the rule definer, and the maintenance cycle for the rule base 140 is shortened. Furthermore, differentiation can be maintained between the rules in the rule base 140 and the rules in the namespace.

[0046] Figure 3 FIG. 3 is a flow chart showing an example of a method 300 for managing a knowledge base according to an embodiment of the present disclosure. For example, the method 300 may be implemented in a Figure 1The method 300 may be executed at the computing device 110 or other suitable device. In addition, the method 300 may include additional steps not shown and / or may omit steps shown, and the scope of the present disclosure is not limited in this respect.

[0047] At 310, computing device 110, in response to receiving a request to modify a rule for first namespace 130, causes the rule to be copied to first namespace 130. Rules are used to constrain structured data in a knowledge base. In some embodiments, computing device 110 may cause the rule to be copied from rule base 140 to first namespace 130. Alternatively, computing device 110 may cause the rule to be copied from second namespace 226 to first namespace 130. First namespace 130 is distinct from second namespace 226. In this manner, the present solution can utilize not only rules in rule base 140 but also rules in other namespaces.

[0048] For example, if first user 120 wishes to customize a rule of a knowledge base associated with first namespace 130, such as first user 120 may wish to customize the standard rule “(Person, wife, Person)” in rule base 140, first user 120 may request modification of the rule from computing device 110. Computing device 110 may cause the requested rule to be copied to first namespace 130. For example, computing device 110 may cause the rule “(Person, wife, Person)” to be copied to first namespace 130.

[0049] At 320, computing device 110 modifies a rule in the first namespace based on the rule modification request for first namespace 130. In some embodiments, computing device 110 may determine a rule modification method for modifying the rule from the rule modification request. Based on the determined rule modification method, computing device 110 may modify one or more entities included in the rule. Additionally or alternatively, computing device 110 may modify the relationship between these entities. In this way, this solution allows for any appropriate modification of rules based on actual user needs for a specific namespace.

[0050] For example, computing device 110 may determine that the rule modification is to modify the entity "Person" in the rule to "Male" and to modify the entity "Person" to "Female", and thus modify the rule "(Person, wife, Person)" to the rule "(Male, wife, Female)".

[0051] At 330, the computing device 110 adds the modified rule from the first namespace 130 to the rule base 140 associated with the knowledge base. In some embodiments, the first user 120 may request that the modified rule be added to the rule base 140, and the computing device 110 may add the modified rule to the rule base 140 in response to the request. In this way, the rule base 140 is augmented with the modified rule, increasing the likelihood that the rules in the rule base 140 meet actual user needs for a particular namespace.

[0052] Additionally or alternatively, in some embodiments, the operation of adding a rule to the rule base requires review by an auditor. In this case, computing device 110 may send a request to the auditor to add the modified rule to rule base 140. If the auditor allows the modified rule to be added to rule base 140, computing device 110 adds the modified rule to rule base 140.

[0053] For example, computing device 110 sends a request to the auditor to add the modified rule to rule base 140 based on the request received from first namespace 130 to add the modified rule to rule base 140. After receiving the request, the auditor reviews whether the modified rule meets the predetermined criteria.

[0054] For example, the predetermined standard may be the way in which the rules are expressed, such as classes and attributes are only allowed to be expressed in English. In this case, the auditor may determine that the rule "(Male, wife, Female)" complies with the way in which the rules are expressed, and allow it to be added to the rule base 140. In addition, the auditor may determine that the rule "(Nanren, wife, Nvren)" does not comply with the way in which the rules are expressed, and refuse to add it to the rule base 140. The auditor then sends a response to the computing device 110 indicating whether the review has been passed. When the computing device 110 receives a response from the auditor indicating that the review has been passed, the computing device 110 adds the rule to the rule base 140. In this way, by increasing the audit link of the auditor, the reliability and effectiveness of the extended rule base are further standardized.

[0055] Optionally, computing device 110 provides the modified rules to third namespace 228 in response to receiving a request to use the modified rules. The third namespace is distinct from the first namespace. For example, if a third user requests to use the rules in first namespace 130, the rules in first namespace 130 (e.g., the rule "(Male, Wife, Female)") may also be copied to third namespace 228 for use or modification. In this way, by allowing modified rules to be directly provided to other namespaces for use, the flexibility and adaptability of the present system are enhanced.

[0056] In some embodiments, computing device 110 can output the rules in the namespace. For example, computing device 110 can output the rules to the user via a visualization page, and can also output the rules in response to a call to the rules. In this way, the present solution can present the rules to the user and provide the rules to the machine in an appropriate manner.

[0057] In this way, semantically identical classes / attributes can be continuously used to achieve rule consistency, extend the maintenance cycle of the rule base 140 , and maintain differentiation between the rules in the rule base 140 and the rules in the namespace.

[0058] Figure 4 FIG. 4 is a schematic block diagram of an apparatus 400 for managing a knowledge base according to an embodiment of the present disclosure. Figure 4 As shown, the device 400 includes: a copy module 410, configured to respond to receiving a request to modify a rule for a first namespace so that the rule is copied to the first namespace, and the rule is used to constrain structured data in a knowledge base; a modification module 420, configured to modify the rule in the first namespace based on the request to modify the rule; and an addition module 430, configured to add the modified rule to a rule base associated with the knowledge base.

[0059] In some embodiments, the replication module 410 includes a rule replication module configured to cause rules to be replicated from at least one of: a rule base, and a second namespace, different from the first namespace, to a first namespace.

[0060] In some embodiments, the modification module 420 includes: a determination module, configured to determine a rule modification method for modifying a rule from a request to modify the rule; and a rule modification module, configured to modify at least one of the following based on the rule modification method: an entity among multiple entities included in the rule, and the relationship between multiple entities.

[0061] In some embodiments, the adding module 430 includes: a rule adding module configured to add the modified rule to the rule base in response to receiving a request from the first namespace to add the modified rule to the rule base. In some embodiments, the rule adding module includes: a sending module configured to send a request to add the modified rule to the rule base; and a review adding module configured to add the modified rule to the rule base in response to receiving a response allowing the modified rule to be added to the rule base.

[0062] In some embodiments, the apparatus 400 further includes a providing module configured to, in response to receiving a request to use the modified rule for the third namespace 228 , provide the modified rule to the third namespace, the third namespace being different from the first namespace.

[0063] In some embodiments, the apparatus 400 further includes at least one of the following: a visualization output module configured to output the modified rule in a visualization manner; and a user programming interface output module configured to output the modified rule in a user programming interface manner.

[0064] Figure 5 Schematic block diagram of an example device 500 that can be used to implement embodiments of the present disclosure. Figure 1 As shown in the figure, the device 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to computer program instructions stored in a read-only memory (ROM) 502 or loaded from a storage unit 508 into a random access memory (RAM) 503. Various programs and data required for the operation of the device 500 can also be stored in the RAM 503. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0065] Various components in device 500 are connected to I / O interface 505, including: an input unit 506, such as a keyboard, mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a magnetic disk, optical disk, etc.; and a communication unit 509, such as a network card, modem, wireless communication transceiver, etc. The communication unit 509 allows device 500 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0066] Processing unit 501 performs the various methods and processes described above, such as process 300. For example, in some embodiments, process 300 may be implemented as a computer software program that is tangibly embodied in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed onto device 500 via ROM 502 and / or communication unit 509. When the computer program is loaded into RAM 503 and executed by CPU 501, one or more steps of process 300 described above may be performed. Alternatively, in other embodiments, CPU 501 may be configured to perform process 300 in any other suitable manner (e.g., via firmware).

[0067] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), and the like.

[0068] The program code for implementing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0069] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0070] In addition, although adopting specific order to describe each operation, this should be understood as requiring such operation to be carried out in the specific order shown or in sequential order, or requiring that all illustrated operations should be carried out to obtain desired results. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although comprising some specific implementation details in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of separate embodiment can also be implemented in a single implementation in combination. On the contrary, the various features described in the context of a single implementation also can be implemented in a plurality of implementations individually or in the mode of any suitable subcombination.

[0071] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A method for managing a knowledge base, comprising: In response to receiving a request to modify a rule for a first namespace, causing the rule to be copied to the first namespace, the rule being used to constrain structured data in a knowledge base; Modify the rule in the first namespace based on the request to modify the rule; adding the modified rules that meet predetermined criteria to a rule base associated with the knowledge base; preserving the dependency relationship between the rules and the modified rules; as well as The actions on the added rules are recorded.

2. The method of claim 1 , wherein causing the rule to be copied to the first namespace comprises: Causes the rules to be copied to the first namespace from at least one of: the rule base, and A second namespace, where the second namespace is different from the first namespace.

3. The method of claim 1 , wherein modifying the rule comprises: determining a rule modification mode for modifying the rule from the request to modify the rule; as well as Based on the rule modification method, modify at least one of the following: an entity from among the entities included in the rule, and The relationships between the multiple entities.

4. The method of claim 1 , wherein adding the modified rule to the rule base comprises: In response to receiving a request to add the modified rule to the rule base from the first namespace, the modified rule is added to the rule base.

5. The method of claim 4 , wherein adding the modified rule to the rule base comprises: sending a request to add the modified rule to the rule base; as well as In response to receiving a response allowing the modified rule to be added to the rule base, the modified rule is added to the rule base.

6. The method according to claim 1, further comprising: In response to receiving a request to use the modified rule for a third namespace, the modified rule is provided to the third namespace, the third namespace being different from the first namespace.

7. The method according to claim 1, further comprising at least one of the following: outputting the modified rules in a visual manner; and The modified rules are outputted in a user programming interface manner.

8. A device for managing a knowledge base, comprising: a copy module configured to, in response to receiving a request to modify a rule for a first namespace, cause the rule to be copied to the first namespace, wherein the rule is used to constrain structured data in a knowledge base; a modification module, configured to modify the rule in the first namespace based on the request to modify the rule; an adding module configured to add the modified rule that meets a predetermined criterion to a rule base associated with the knowledge base; a retaining module configured to retain the dependency relationship between the rules and the modified rules; as well as A recording module is configured to record actions on the added rules.

9. The apparatus according to claim 8, wherein the copy module comprises: A rule replication module is configured to cause the rule to be copied to the first namespace from at least one of the following: the rule base, and A second namespace, where the second namespace is different from the first namespace.

10. The apparatus according to claim 8, wherein the modification module comprises: a determination module configured to determine a rule modification mode for modifying the rule from the request for modifying the rule; as well as A rule modification module is configured to modify at least one of the following based on the rule modification method: an entity from among the entities included in the rule, and at least one of the relationships between the plurality of entities.

11. The apparatus according to claim 8, wherein the adding module comprises: The rule adding module is configured to add the modified rule to the rule base in response to receiving a request to add the modified rule to the rule base from the first namespace.

12. The apparatus according to claim 11, wherein the rule adding module comprises: a sending module configured to send a request to add the modified rule to the rule base; as well as The audit adding module is configured to add the modified rule to the rule base in response to receiving a response allowing the modified rule to be added to the rule base.

13. The apparatus according to claim 8, further comprising: A providing module is configured to provide the modified rule to a third namespace in response to receiving a request to use the modified rule for the third namespace, the third namespace being different from the first namespace.

14. The apparatus of claim 8, further comprising at least one of the following: a visualization output module configured to output the modified rules in a visualization manner; and The user programming interface output module is configured to output the modified rules in a user programming interface manner.

15. An electronic device, comprising: one or more processors; as well as A storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method according to claims 1 to 7.

16. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images