A method, apparatus, equipment, and medium for enhancing information retrieval and generating conclusion verification.

By recording the basis for the formation and validity status of conclusion units in the retrieval enhancement generation system, establishing dependencies, and locating and verifying conclusion units when evidence or rules change, the problem of the inability to accurately verify affected conclusions in existing systems is solved, thereby improving the stability of the system and the accuracy of verification results.

CN123115504APending Publication Date: 2026-11-17四川长虹新网科技有限责任公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611506398.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-27
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing retrieval enhancement generation and large language model reasoning systems cannot accurately determine the affected conclusions and their necessary review operations when the versions of external evidence or processing rules change, resulting in irrelevant retrieval and reasoning, and failing to retain the evidence and conclusion status before and after review.

Method used

By acquiring retrieval evidence from knowledge documents and web pages, a conclusion unit with retrieval evidence references is generated, and the basis for its formation and validity status are recorded. The dependency between the conclusion unit and the evidence version, the processing rule version, and the prerequisites for task actions is established. After receiving a change event, the affected conclusion unit is located and a review obligation is generated. The review is performed and the validity status of the conclusion and the output fragment are updated.

Benefits of technology

It enables accurate verification of affected conclusions, avoids irrelevant searches and inferences, and improves the stability of the search enhancement system and the accuracy of verification results.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123115504A_ABST
    Figure CN123115504A_ABST
Patent Text Reader

Abstract

This application provides a method, apparatus, device, and medium for enhancing information retrieval and verifying conclusions, belonging to the field of information retrieval technology. By establishing type dependencies between conclusion units and evidence versions, processing rule versions, other conclusion units, output fragments, and task action premises during the formation and referencing of conclusion units, the application accurately identifies affected conclusions and their necessary verification operations, avoiding irrelevant searches and inferences, thereby improving the stability of retrieval enhancement. The application verifies affected conclusion units and updates the conclusion validity status and associated verification result versions based on the verification results. Based on the conclusion validity status and verification results, it updates the output fragments referencing affected conclusion units and / or controls task actions based on affected conclusion units. The application retains the evidence, conclusion status, and verification results before and after verification, improving the accuracy of the verification results.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of information retrieval technology, and specifically relates to an information retrieval enhancement method, apparatus, equipment and medium for generating and verifying conclusions. Background Technology

[0002] Retrieval-enhanced generation systems typically retrieve evidence from knowledge documents, web pages, or knowledge bases, and then provide this evidence to a large language model to generate research responses, structured judgments, or recommendations. For traceability, the output can cite the evidence used; in agent-based scenarios, the system may also invoke retrieval tools, analysis tools, publishing tools, or external business systems based on the conclusions.

[0003] After a conclusion has been reached, output has been displayed, or task actions have established the prerequisites for the conclusion, the content, source status, or validity status of the cited evidence may change; the processing rules for the quantity, source, acceptance, conflict resolution, presentation of citations, and prerequisites for task actions may also change. Existing systems often handle changes by re-searching, re-reasoning, and regenerating all outputs, causing unaffected conclusions to repeatedly consume computational resources.

[0004] Another type of system only synchronizes source records, knowledge nodes, or output text, and cannot distinguish whether an existing conclusion should be re-accepted, evidence conflicts should be resolved, partial re-retrieval should be performed, partial re-reasoning should be conducted, output should be updated, or it is a prerequisite for verification tasks. Therefore, conclusions that are pending review, revoked, or whose conflicts remain unresolved may still be displayed or used as the basis for tool calls and external actions.

[0005] Based on the above-mentioned existing technologies, the following deficiencies exist: In systems where retrieval enhancement generation and large language model inference have already formed cited conclusions, how can we accurately determine the affected conclusions and their necessary review operations when subsequent events such as changes in external evidence versions or processing rule versions arrive, and avoid irrelevant retrieval and inference; how can we retain the basis, conclusion status, and review results before and after review; and how can we update the output and control task actions separately to prevent unreliable conclusions from continuing to drive external effects.

[0006] In systems where retrieval enhancement generation and large language model reasoning have already formed cited conclusions, when subsequent events such as changes in external evidence versions or processing rule versions arrive, it is impossible to accurately determine the affected conclusions and their necessary verification operations, resulting in irrelevant retrieval and reasoning. Summary of the Invention

[0007] In view of the above problems, embodiments of this application provide, in one aspect, an information retrieval enhancement method for generating conclusion verification, including:

[0008] Acquire retrieval evidence from knowledge documents, web pages, and knowledge bases, and generate conclusion units with retrieval evidence references based on the retrieval evidence and a set of rules for machine-executable processing;

[0009] When the conclusion unit is formed or the output segment of the conclusion unit is referenced, the basis for the formation of the conclusion unit and the validity status of the conclusion are recorded;

[0010] Establish type dependencies between the conclusion unit and the evidence version, processing rule version, other conclusion units, output fragments, and task action premises;

[0011] Receive external evidence version change events or processing rule version change events that occur after the conclusion unit is formed; based on the change events, the type dependencies, and the processing rules applicable to the conclusion unit, locate the affected conclusion unit and generate a review obligation for the affected conclusion unit;

[0012] Perform the aforementioned review obligation, review the affected conclusion unit, and update the validity status of the conclusion and the associated review result version based on the review results;

[0013] Based on the validity status of the conclusion and the verification result, update the output segment referencing the affected conclusion unit and / or control the task actions based on the affected conclusion unit.

[0014] Furthermore, the step of locating the affected conclusion unit based on the change event, the type dependency, and the processing rules applicable to the conclusion unit, and generating a review obligation for the affected conclusion unit, includes:

[0015] Each review obligation is associated with the target conclusion unit, the change event, the applicable processing rules, the validity judgment to be obtained, and the independent triggering purpose of the review result;

[0016] Only when the combined review obligation and the review obligation to be merged target the same objective conclusion unit, the same change event and the same applicable processing rule, the review result obtained by the combined review obligation includes all the validity judgments required by the review obligation to be merged.

[0017] Furthermore, when the review result of the review obligation to be merged is not used to independently trigger the output fragment update or the task action premise verification, the review obligation to be merged will be incorporated into the combined review obligation.

[0018] Furthermore, the step of reviewing the affected conclusion unit and updating the validity status of the conclusion and the associated review result version based on the review result includes:

[0019] Update the validity status of the conclusion, update the output fragment, and verify the prerequisites for the task actions;

[0020] When the independent triggering purpose includes updating the validity status of the conclusion, the target conclusion unit is set to the pending review state, and unstarted task actions that are based on the target conclusion unit are frozen.

[0021] When the independent triggering purpose only includes verifying the prerequisites for the task action, the relevant unstarted task action is frozen without changing the conclusion validity state of the target conclusion unit.

[0022] Furthermore, performing the review obligation includes:

[0023] Perform at least one of the following operations on the affected conclusion unit: re-acceptance, conflict checking, local re-retrieval, and local re-reasoning;

[0024] When a re-acceptance or conflict check fails to meet the processing rules, or when the processing rules require a new conclusion, the local re-retrieval and / or local re-reasoning are performed.

[0025] Furthermore, updating the output segment referencing the affected conclusion unit and / or controlling task actions based on the affected conclusion unit according to the validity status of the conclusion and the review result includes:

[0026] When the content of the evidence directly supporting the conclusion unit is changed or deleted, the source status becomes invalid, or the validity status changes, the review obligation includes re-acceptance;

[0027] If the re-acceptance does not meet the processing rules, local re-search and local re-reasoning are performed.

[0028] Furthermore, the method also includes: when the evidence quantity condition, source condition, acceptance condition, or reasoning constraint in the research constraint subset of the processing rule version changes, the review obligation includes re-acceptance;

[0029] When the evidence to refute or limit the evidence changes, or when the conflict resolution rules change, the review obligation includes conflict checking.

[0030] When an upstream conclusion unit is connected to the conclusion unit through a conclusion derivation relationship and the validity status of the conclusion of the upstream conclusion unit changes, a derived conclusion review obligation is generated for the conclusion unit.

[0031] Furthermore, the method also includes: writing the validity status of the conclusion as "continued to be valid", "replaced", "revoked", "pending review" or "conflict unresolved" according to the review result, and retaining the review result version of the basis for formation or review result before the change event occurred, as well as the review result version of the evidence or processing rules associated with the change.

[0032] When the review results indicate that the conclusion content has not changed, but the review of evidence conditions, acceptance conditions, conflict resolution, or reasoning constraints has been completed, the version of the review result that remains valid after the relevant changes in evidence or processing rules is retained.

[0033] Based on the same inventive concept, a third aspect of the embodiments of this application also provides an information retrieval enhancement conclusion verification device, comprising:

[0034] An evidence acquisition unit is used to acquire retrieval evidence from knowledge documents, web pages, and knowledge bases, and to generate a conclusion unit with retrieval evidence references based on the retrieval evidence and a set of rules for machine-executable processing.

[0035] A status recording unit is used to record the basis for the formation of the conclusion unit and the validity status of the conclusion unit when the conclusion unit is formed or when the output fragment of the conclusion unit is referenced.

[0036] A dependency establishment unit is used to establish typed dependencies between the conclusion unit and the evidence version, processing rule version, other conclusion units, output fragments, and task action premises;

[0037] An obligation generation unit is configured to receive external evidence version change events or processing rule version change events that occur after the conclusion unit is formed; based on the change events, the type dependencies, and the processing rules applicable to the conclusion unit, locate the affected conclusion unit, and generate a review obligation for the affected conclusion unit;

[0038] An obligation execution unit is used to execute the review obligation, review the affected conclusion unit, and update the validity status of the conclusion and the associated review result version based on the review result;

[0039] The task control unit is used to update the output segment referencing the affected conclusion unit and / or control the task actions based on the affected conclusion unit, according to the validity status of the conclusion and the review result.

[0040] Based on the same inventive concept, a second aspect of the present application also provides an electronic device, characterized in that it includes: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0041] Memory, which stores computer programs;

[0042] When the processor executes a program stored in memory, it implements an information retrieval enhancement method to generate conclusion verification.

[0043] Based on the same inventive concept, the fourth aspect of the present application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements an information retrieval enhancement generation conclusion verification method.

[0044] The beneficial effects of this application are:

[0045] Based on the above technical solution, when the conclusion unit is formed and its output fragment is referenced, the basis for its formation and the validity status of the conclusion are recorded; a typed dependency is established between the conclusion unit and the evidence version, processing rule version, other conclusion units, output fragments, and task action premises; external evidence version change events or processing rule version change events that occur after the conclusion unit is formed are received; based on the change events, the typed dependencies, and the processing rules applicable to the conclusion unit, the affected conclusion units are located, and a review obligation is generated for the affected conclusion units; the affected conclusions and their necessary review operations are accurately determined, irrelevant searches and inferences are avoided, thereby improving the stability of the search enhancement.

[0046] By reviewing the affected conclusion units and updating the validity status of the conclusions and the associated review result versions based on the review results, the output segments referencing the affected conclusion units and / or the task actions controlling the affected conclusion units are updated based on the validity status of the conclusions and the review results. The system retains the evidence, conclusion status, and review results before and after the review, thus improving the accuracy of the review results.

[0047] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures pointed out in the description and the accompanying drawings. Attached Figure Description

[0048] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1 A flowchart of an information retrieval enhancement method for generating and verifying conclusions is shown.

[0050] Figure 2 A schematic diagram of an information retrieval enhancement conclusion verification device is shown.

[0051] Figure 3A schematic diagram of an electronic device for implementing the method of this embodiment is shown. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0053] It should be noted that the terms "first," "second," etc., used in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. In this application, the terms "upper," "lower," "left," "right," "front," "rear," "top," "bottom," "inner," "outer," "middle," "vertical," "horizontal," "lateral," "longitudinal," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings.

[0054] This application provides, in one aspect, a method for enhancing information retrieval and verifying conclusions generated, see [link to relevant documentation]. Figure 1 ,include:

[0055] Acquire retrieval evidence from knowledge documents, web pages, and knowledge bases, and generate conclusion units with retrieval evidence references based on the retrieval evidence and a set of rules for machine-executable processing;

[0056] When the conclusion unit is formed or the output segment of the conclusion unit is referenced, the basis for the formation of the conclusion unit and the validity status of the conclusion are recorded;

[0057] Establish type dependencies between the conclusion unit and the evidence version, processing rule version, other conclusion units, output fragments, and task action premises;

[0058] Receive external evidence version change events or processing rule version change events that occur after the conclusion unit is formed; based on the change events, the type dependencies, and the processing rules applicable to the conclusion unit, locate the affected conclusion unit and generate a review obligation for the affected conclusion unit;

[0059] Perform the aforementioned review obligation, review the affected conclusion unit, and update the validity status of the conclusion and the associated review result version based on the review results;

[0060] Based on the validity status of the conclusion and the verification result, update the output segment referencing the affected conclusion unit and / or control the task actions based on the affected conclusion unit.

[0061] The information retrieval enhancement generation conclusion verification method in the embodiments of this specification is typically applied in a server, which can be a cloud server or a local server. The server can be an electronic device such as a laptop, desktop computer, tablet computer, or all-in-one computer.

[0062] Specifically, the embodiments of this application include the following steps:

[0063] a. Records of the basis for the conclusions.

[0064] The retrieval enhancement generation processing unit obtains evidence versions from knowledge documents, web pages, or knowledge bases; the large language model reasoning unit generates conclusion units with evidence citations based on the evidence and a set of machine-executable processing rules. Each conclusion unit is associated with at least the conclusion content, conclusion type, basis for formation, formation time, current validity status of the conclusion, and a version of the verification result. The basis for formation includes directly cited evidence versions and upstream conclusion units that form the basis for formation.

[0065] b. Rule application records.

[0066] For each conclusion unit, a rule application record is created. This record includes the rule identifier, processing rule version, applicable subset of research constraints, subset of output constraints, subset of task action constraints, rule condition items, scope of application, rule condition verification results at the time of conclusion formation, and a validity flag. The scope of application may include one or more of the following: conclusion object or topic, time or region, and task action type.

[0067] c. There is a type dependency.

[0068] The system establishes typed dependencies between conclusion units and evidence versions, processing rule versions, other conclusion units, output fragments, and task action premises. The uses of these dependencies include at least direct support, rebuttal, limitation, conclusion derivation, output presentation, and task action premises, thereby distinguishing the role of evidence in establishing a conclusion, the derivational relationships between conclusions, the reference relationships between outputs and conclusions, and the dependencies of task actions on conclusions.

[0069] d. Change and review process.

[0070] The system receives evidence version change events or processing rule version change events. Evidence version change events include at least the evidence identifier, the previous version, the new version, the change category, and the time of occurrence; processing rule version change events include at least the rule identifier, the previous version, the new version, the rule subset type, the rule condition item that changed, the scope of application of the change, the change category, and the time of occurrence.

[0071] For evidence version change events, the system locates the initial affected conclusion based on the evidence identifier, the version before the change, and valid dependencies. For rule version change events, the system only determines the associated conclusion as the affected conclusion when the rule identifiers are consistent, the versions before the change are consistent, the rule subsets are consistent, the rule conditions intersect, the applicable scopes intersect, and the valid flags are valid.

[0072] The system generates review obligations for the affected conclusions. A review obligation must at least be associated with the target conclusion, the changing event, the applicable processing rules, the required validity assessment, the scope of execution, and the independent triggering purpose. Review obligations may include re-acceptance, conflict checking, partial re-retrieval, partial re-reasoning, output fragment updates, or task action prerequisite verification.

[0073] e. Output update and task action control.

[0074] The system updates the validity status of conclusions based on the review results, indicating whether they remain valid, have been superseded, revoked, pending review, or have unresolved conflicts. It also retains the review result versions before the changes in the supporting evidence or processing rules, as well as the versions of evidence or processing rules after the changes. Only output segments referencing the affected conclusions are updated; output segments not referencing the affected conclusions remain unchanged.

[0075] Before invoking tools, submitting external content, or generating external effects, the task executor reads the validity status of the conclusions associated with the task action prerequisites and the completion status of the task action prerequisite verification obligations. If the conclusion is in a pending review, revocation, or conflict unresolved state, or if the task action prerequisite verification obligations are not completed, the task action is frozen or refused to start; once the prerequisites are met and verification is completed, the task action is unfrozen or started.

[0076] Specifically, the step of locating the affected conclusion unit based on the change event, the type dependency, and the processing rules applicable to the conclusion unit, and generating a review obligation for the affected conclusion unit, includes:

[0077] Each review obligation is associated with the target conclusion unit, the change event, the applicable processing rules, the validity judgment to be obtained, and the independent triggering purpose of the review result;

[0078] Only when the combined review obligation and the review obligation to be merged target the same objective conclusion unit, the same change event and the same applicable processing rule, the review result obtained by the combined review obligation includes all the validity judgments required by the review obligation to be merged.

[0079] Furthermore, when the review result of the review obligation to be merged is not used to independently trigger the output fragment update or the task action premise verification, the review obligation to be merged will be incorporated into the combined review obligation.

[0080] Specifically, the step of reviewing the affected conclusion unit and updating the validity status of the conclusion and the associated review result version based on the review results includes:

[0081] Update the validity status of the conclusion, update the output fragment, and verify the prerequisites for the task actions;

[0082] When the independent triggering purpose includes updating the validity status of the conclusion, the target conclusion unit is set to the pending review state, and unstarted task actions that are based on the target conclusion unit are frozen.

[0083] When the independent triggering purpose only includes verifying the prerequisites for the task action, the relevant unstarted task action is frozen without changing the conclusion validity state of the target conclusion unit.

[0084] Specifically, performing the review obligation includes performing at least one of the following operations on the affected conclusion unit: re-acceptance, conflict checking, local re-retrieval, and local re-reasoning;

[0085] When a re-acceptance or conflict check fails to meet the processing rules, or when the processing rules require a new conclusion, the local re-retrieval and / or local re-reasoning are performed.

[0086] Specifically, updating the output segment referencing the affected conclusion unit and / or controlling task actions based on the affected conclusion unit according to the validity status of the conclusion and the review result includes:

[0087] When the content of the evidence directly supporting the conclusion unit is changed or deleted, the source status becomes invalid, or the validity status changes, the review obligation includes re-acceptance;

[0088] If the re-acceptance does not meet the processing rules, local re-search and local re-reasoning are performed.

[0089] Specifically, the method further includes: when the evidence quantity condition, source condition, acceptance condition or reasoning constraint in the research constraint subset of the processing rule version changes, the review obligation includes re-acceptance;

[0090] When the evidence to refute or limit the evidence changes, or when the conflict resolution rules change, the review obligation includes conflict checking.

[0091] When an upstream conclusion unit is connected to the conclusion unit through a conclusion derivation relationship and the validity status of the conclusion of the upstream conclusion unit changes, a derived conclusion review obligation is generated for the conclusion unit.

[0092] Specifically, the method further includes: writing the validity status of the conclusion as "continued to be valid", "replaced", "revoked", "pending review" or "conflict unresolved" according to the review result, and retaining the review result version of the basis for formation or review result before the change event occurred, as well as the review result version of the evidence or processing rules associated with the change;

[0093] When the review results indicate that the conclusion content has not changed, but the review of evidence conditions, acceptance conditions, conflict resolution, or reasoning constraints has been completed, the version of the review result that remains valid after the relevant changes in evidence or processing rules is retained.

[0094] The present invention is illustrated below using scenarios involving research report agents and knowledge base service agents. This implementation clarifies the targeted review, partial output updates, and task action control triggered by external version changes after the conclusions are formed, and does not limit the scope of protection of the present invention.

[0095] A. Record of conclusion generation and formation basis:

[0096] The research report agent receives a request asking whether a certain technology object satisfies condition P and can be used in scenario Q. The system retrieves Evidence Version 1 (A), Evidence Version 1 (B), and Evidence Version 1 (C) from its internal technical knowledge base and publicly available technical materials. Based on the research constraint of "at least two valid independent pieces of evidence," the large language model forms conclusion unit A, "The technology object satisfies condition P," and cites Evidence Version 1 (A) and Evidence Version 1 (B). Then, using conclusion unit A as the basis, conclusion unit B, "The technology object can be used in scenario Q," is generated. The output fragment A of the research report cites conclusion unit B.

[0097] B. Rule application records:

[0098] The system persists rule application records for Conclusion Unit A and Conclusion Unit B respectively. Each record includes the research constraint rule identifier, rule version, evidence quantity condition, technical subject scope, and verification results at the time of formation; it also includes the subset of output constraints applicable to research report citations and the subset of task action constraints applicable to external evaluation requests. The validity marker of the rule application record is adjusted after the conclusion is replaced or revoked to prevent historical records from being used as the current rule application object again.

[0099] C. Type dependency exists:

[0100] The system establishes direct supporting dependencies for conclusion unit A (consistent with version A of evidence A), conclusion derivation dependencies from conclusion unit A to conclusion unit B, output presentation dependencies from conclusion unit B to output fragment A, and task action prerequisite dependencies from conclusion unit B to task action prerequisite A. Task action prerequisite A stipulates that an evaluation request can only be submitted to an external evaluation tool when conclusion unit B remains valid and the action prerequisite verification is completed.

[0101] D. Change and Review Process:

[0102] D1. Handling of changes in evidence versions;

[0103] External technical data release evidence version A is version two, and the supporting condition P has been deleted. After verifying that evidence version one and version two are traceable versions of the same evidence, the system locates conclusion unit A based on the evidence identifier, the version before the change, and the direct supporting dependencies; then it locates conclusion unit B along the conclusion derivation dependencies, and locates output fragment A and the external evaluation request along the output presentation dependencies and task action prerequisite dependencies, respectively.

[0104] The system generates a re-acceptance obligation for conclusion unit A and a derived conclusion review obligation for conclusion unit B, and also generates an output fragment update obligation and a task action premise verification obligation, respectively. If the remaining evidence does not meet the requirement of "at least two qualified independent pieces of evidence", the system will only conduct supplementary searches within the subject area of ​​condition P and only re-form conclusion unit A and its derived conclusion unit B; it will not perform searches or inferences on report content for which no dependencies have been established.

[0105] D2. Handling rule version changes;

[0106] The knowledge base service agent generates conclusion unit C, stating that "the service application meets the processing conditions," and prepares to submit the application to the external business system based on task action prerequisite B. Subsequently, the task action constraint rules are changed from version three to version four, with the changed rule condition being the automatic submission condition, and the scope of application being the service type and applicable region.

[0107] The system matches the rule application records of Conclusion Unit C based on six conditions: rule identifier, previous version, rule subset type, intersection of rule conditions, intersection of applicable scope, and validity flag. Since this change does not involve the basis for conclusion formation, research constraints, or output constraints, the system only generates the task action prerequisite verification obligation and freezes applications that have not yet been submitted; it does not re-accept Conclusion Unit C, nor does it update the response output fragment.

[0108] E. Output Update and Task Action Control:

[0109] For the processing result of D1, if the supplementary evidence meets the research constraints, the system will write the original conclusion as either replaced or still valid, save the verification result version of the old and new evidence, and only replace output fragment A; before actually submitting the evaluation request, the task executor will re-verify the prerequisites for the task action. If the supplementary evidence still does not meet the research constraints, the relevant conclusion will be written as withdrawn or the conflict is unresolved, the output fragment will display the corresponding status, and the task action will remain frozen or be changed to rejected.

[0110] Regarding the processing result of D2, if the prerequisite for the new action is met, the system saves the conclusion status and rule application record, and changes the task action from pending verification to allowed to start and submit application; if not met, the task action changes to rejected. Thus, rule changes only affect actions that have not yet produced external effects, and do not trigger repeated processing of irrelevant conclusions and outputs.

[0111] Based on the same inventive concept, a third aspect of the embodiments of this application also provides an information retrieval enhancement conclusion verification device, see [link to relevant documentation]. Figure 2 ,include:

[0112] An evidence acquisition unit is used to acquire retrieval evidence from knowledge documents, web pages, and knowledge bases, and to generate a conclusion unit with retrieval evidence references based on the retrieval evidence and a set of rules for machine-executable processing.

[0113] A status recording unit is used to record the basis for the formation of the conclusion unit and the validity status of the conclusion unit when the conclusion unit is formed or when the output fragment of the conclusion unit is referenced.

[0114] A dependency establishment unit is used to establish typed dependencies between the conclusion unit and the evidence version, processing rule version, other conclusion units, output fragments, and task action premises;

[0115] An obligation generation unit is configured to receive external evidence version change events or processing rule version change events that occur after the conclusion unit is formed; based on the change events, the type dependencies, and the processing rules applicable to the conclusion unit, locate the affected conclusion unit, and generate a review obligation for the affected conclusion unit;

[0116] An obligation execution unit is used to execute the review obligation, review the affected conclusion unit, and update the validity status of the conclusion and the associated review result version based on the review result;

[0117] The task control unit is used to update the output segment referencing the affected conclusion unit and / or control the task actions based on the affected conclusion unit, according to the validity status of the conclusion and the review result.

[0118] Based on the same inventive concept, this disclosure also provides an electronic device 161, see [link to previous document]. Figure 3 It includes a processor 164, a communication interface 165, a memory 162, and a communication bus, wherein the processor 164, the communication interface 165, and the memory 162 communicate with each other through the communication bus;

[0119] Memory 162 stores computer program 163;

[0120] When processor 164 executes the program stored in memory 162, it implements the information retrieval enhancement generation conclusion verification method.

[0121] The aforementioned communication bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc.

[0122] The communication interface 165 is used for communication between the aforementioned electronic device 161 and other devices.

[0123] The memory 162 may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory 162 may also be at least one storage device located remotely from the aforementioned processor 164.

[0124] The processor 164 mentioned above can be a general-purpose processor 164, including a central processing unit (CPU), a network processor (NP), etc.; it can 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 gate or transistor logic devices, or discrete hardware components.

[0125] Based on the same inventive concept, another aspect of the present disclosure provides a computer-readable storage medium storing a computer program 163, which, when executed by a processor 164, implements the aforementioned information retrieval enhancement generation conclusion verification method.

[0126] The computer-readable storage medium may be included in the device / apparatus described in the above embodiments; or it may exist independently and not assembled into the device / apparatus. The computer-readable storage medium carries one or more programs, which, when executed, implement the information retrieval enhancement generation conclusion verification method according to the embodiments of this disclosure.

[0127] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for verifying conclusions generated through enhanced information retrieval, characterized in that, include: Acquire retrieval evidence from knowledge documents, web pages, and knowledge bases, and generate conclusion units with retrieval evidence references based on the retrieval evidence and a set of rules for machine-executable processing; When the conclusion unit is formed or the output segment of the conclusion unit is referenced, the basis for the formation of the conclusion unit and the validity status of the conclusion are recorded; Establish type dependencies between the conclusion unit and the evidence version, processing rule version, other conclusion units, output fragments, and task action premises; Receive external evidence version change events or processing rule version change events that occur after the conclusion unit is formed; based on the change events, the type dependencies, and the processing rules applicable to the conclusion unit, locate the affected conclusion unit and generate a review obligation for the affected conclusion unit; Perform the aforementioned review obligation, review the affected conclusion unit, and update the validity status of the conclusion and the associated review result version based on the review results; Based on the validity status of the conclusion and the verification result, update the output segment referencing the affected conclusion unit and / or control the task actions based on the affected conclusion unit.

2. The method according to claim 1, characterized in that, The process of locating affected conclusion units based on the change event, the type dependency, and the processing rules applicable to the conclusion units, and generating review obligations for the affected conclusion units, includes: Each review obligation is associated with the target conclusion unit, the change event, the applicable processing rules, the validity judgment to be obtained, and the independent triggering purpose of the review result; Only when the combined review obligation and the review obligation to be merged target the same objective conclusion unit, the same change event and the same applicable processing rule, the review result obtained by the combined review obligation includes all the validity judgments required by the review obligation to be merged. Furthermore, when the review result of the review obligation to be merged is not used to independently trigger the output fragment update or the task action premise verification, the review obligation to be merged will be incorporated into the combined review obligation.

3. The method according to claim 1, characterized in that, The step of reviewing the affected conclusion unit and updating the validity status of the conclusion and the associated review result version based on the review results includes: Update the validity status of the conclusion, update the output fragment, and verify the prerequisites for the task actions; When the independent triggering purpose includes updating the validity status of the conclusion, the target conclusion unit is set to the pending review state, and unstarted task actions that are based on the target conclusion unit are frozen. When the independent triggering purpose only includes verifying the prerequisites for the task action, the relevant unstarted task action is frozen without changing the conclusion validity state of the target conclusion unit.

4. The method according to claim 2 or 3, characterized in that, The execution of the review obligation includes: Perform at least one of the following operations on the affected conclusion unit: re-acceptance, conflict checking, local re-retrieval, and local re-reasoning; When a re-acceptance or conflict check fails to meet the processing rules, or when the processing rules require a new conclusion, the local re-retrieval and / or local re-reasoning are performed.

5. The method according to claim 1, characterized in that, The step of updating the output segment referencing the affected conclusion unit and / or controlling task actions based on the affected conclusion unit according to the validity status of the conclusion and the review result includes: When the content of the evidence directly supporting the conclusion unit is changed or deleted, the source status becomes invalid, or the validity status changes, the review obligation includes re-acceptance; If the re-acceptance does not meet the processing rules, local re-search and local re-reasoning are performed.

6. The method according to claim 5, characterized in that, The method further includes: When the evidence quantity condition, source condition, acceptance condition, or reasoning constraint in the research constraint subset of the processing rule version changes, the review obligation includes re-acceptance; When the evidence to refute or limit the evidence changes, or when the conflict resolution rules change, the review obligation includes conflict checking. When an upstream conclusion unit is connected to the conclusion unit through a conclusion derivation relationship and the validity status of the conclusion of the upstream conclusion unit changes, a derived conclusion review obligation is generated for the conclusion unit.

7. The method according to claim 6, characterized in that, The method further includes: The validity status of the conclusion is recorded according to the review results: continued validity, replaced, revoked, pending review, or unresolved conflict. The review results version of the basis for formation or review results before the change event occurred, as well as the version of the evidence or processing rules after the related change, are also retained. When the review results indicate that the conclusion content has not changed, but the review of evidence conditions, acceptance conditions, conflict resolution, or reasoning constraints has been completed, the version of the review result that remains valid after the relevant changes in evidence or processing rules is retained.

8. An information retrieval enhancement conclusion verification device, characterized in that, include: An evidence acquisition unit is used to acquire retrieval evidence from knowledge documents, web pages, and knowledge bases, and to generate a conclusion unit with retrieval evidence references based on the retrieval evidence and a set of rules for machine-executable processing. A status recording unit is used to record the basis for the formation of the conclusion unit and the validity status of the conclusion unit when the conclusion unit is formed or when the output fragment of the conclusion unit is referenced. A dependency establishment unit is used to establish typed dependencies between the conclusion unit and the evidence version, processing rule version, other conclusion units, output fragments, and task action premises; An obligation generation unit is configured to receive external evidence version change events or processing rule version change events that occur after the conclusion unit is formed; based on the change events, the type dependencies, and the processing rules applicable to the conclusion unit, locate the affected conclusion unit, and generate a review obligation for the affected conclusion unit; An obligation execution unit is used to execute the review obligation, review the affected conclusion unit, and update the validity status of the conclusion and the associated review result version based on the review result; The task control unit is used to update the output segment referencing the affected conclusion unit and / or control the task actions based on the affected conclusion unit, according to the validity status of the conclusion and the review result.

9. An electronic device, characterized in that, include: The processor, communication interface, memory, and communication bus are connected, with the processor, communication interface, and memory communicating with each other via the communication bus. Memory, which stores computer programs; When the processor executes the program stored in the memory, it implements the information retrieval enhancement generation conclusion verification method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The system contains a computer program that, when executed by a processor, implements the information retrieval enhancement generation conclusion verification method according to any one of claims 1 to 7.