A text auditing method based on entity relationship verification

Abstract

The application discloses a kind of text auditing methods based on entity relationship verification, comprising: the application divides the text to be audited according to project phase and forms entity relationship edge with stage position, and the entity relationship scattered in project establishment, task, achievement and acceptance material is converted into checkable relationship object;By stage relationship direction table matching standard direction relationship, make the entity relationship audit have project stage sequence benchmark and undertake node constraint;Then by start-end stage comparison and undertake node search, identify stage direction inversion and missing cross-stage undertaking, avoid false judgment text compliance by only relying on the existence of keyword;Finally, locate abnormal paragraph and corresponding entity relationship edge, form the text auditing result with relationship level evidence;Therefore, the application improves the logical consistency, abnormal positioning accuracy and review efficiency of power scientific research project text before storage auditing.

Description

Technical Field

[0001] This invention relates to the technical field of project text review, and in particular to a text review method based on entity relationship verification. Background Technology

[0002] The pre-entry review of documents throughout the entire lifecycle of power research projects typically involves project proposals, project task books, implementation plans, mid-term inspection materials, deliverables lists, testing and verification materials, acceptance reports, and rectification materials. These documents contain numerous entities, including project name, project number, undertaking unit, research object, technical problem, research task, technical route, assessment indicators, deliverable names, testing materials, acceptance opinions, and acceptance conclusions. Existing review methods largely rely on manual item-by-item verification, keyword matching, format rule validation, or text similarity comparison. While these methods can identify superficial issues such as missing chapters, repetitive expressions, and blank fields, they struggle to determine whether the entity relationships between different project stages conform to the chronological logic of project initiation, task, deliverables, and acceptance. In particular, they are difficult to identify issues such as acceptance conclusions pointing back to research tasks, deliverables materials interpreting project objectives in reverse, and task content directly connecting to acceptance conclusions across deliverables—all examples of reversed stage logic. Therefore, the problem this invention aims to solve is how to automatically review the direction of cross-stage entity relationships and stage continuity before power research project documents are entered into the database.

[0003] In existing text review technologies, entity extraction and relation extraction typically focus on single texts or paragraphs, emphasizing the identification of entity names, relational predicates, and local semantic collocations. They lack a relational direction benchmark oriented towards the phase sequence of research projects. For power research projects, the same research object may span multiple phases, including project initiation, tasks, deliverables, and acceptance. Simply extracting relationships such as research task-deliverable name and deliverable name-acceptance conclusion cannot determine whether the relationship is in the correct phase direction, nor can it determine whether necessary intermediate connecting nodes are missing in cross-phase relationships. For example, assessment indicators in the task phase should be supported by deliverable materials in the deliverable phase and test materials in the acceptance phase. If the text directly shows assessment indicators corresponding to acceptance conclusions without corresponding deliverable materials, existing rule-based review often only checks for the presence of keywords, failing to locate the missing entity relation edges and their corresponding paragraphs.

[0004] Furthermore, power research project documents are highly specialized and phased. There is a clear textual organization order and business succession relationship between the research objects, experimental objects, result types, and acceptance indicators in the project materials. Existing general text review technologies usually do not establish a phase relationship direction table that includes the project phase sequence, entity type, relationship type, and succession node. This results in the lack of traceable standard direction relationships in the review results, making it difficult to explain to reviewers the reasons for the formation of abnormal paragraphs, abnormal types, and abnormal entity relationship edges. Summary of the Invention

[0005] The purpose of this section is to outline some aspects of the embodiments of the present invention and to briefly introduce some preferred embodiments. Some simplifications or omissions may be made in this section, as well as in the specification abstract and the title of the invention, to avoid obscuring the purpose of this section, the specification abstract, and the title of the invention. Such simplifications or omissions shall not be used to limit the scope of the invention.

[0006] In view of the aforementioned existing problems, the present invention is proposed.

[0007] To solve the above-mentioned technical problems, the present invention provides the following technical solution: A text review method based on entity relationship verification includes: dividing the text to be reviewed into project stages, extracting stage entities, task entities, result entities and acceptance entities from the text to be reviewed, and forming entity relationship edges with stage positions; Based on the project phase sequence, entity type, and relationship type, establish a phase relationship direction table containing receiving nodes, and match standard directional relationships in the phase relationship direction table according to the entity type and relationship type of the entity relationship edge. The relationship start stage and relationship end stage of the entity relationship edge are compared with the preceding stage and following stage in the standard directional relationship, and entity relationship edges with opposite start and end stages and entity relationship edges lacking a receiving node are marked. Based on the marking results, identify paragraphs with abnormal relationship directions and their corresponding entity relationship edges, and generate text review results.

[0008] The beneficial effects of this invention are as follows: This invention divides the text to be reviewed according to project stages and forms entity relationship edges with stage positions, transforming the entity relationships scattered in project initiation, tasks, results, and acceptance materials into verifiable relationship objects; by matching standard directional relationships through a stage relationship direction table, the entity relationship review has a project stage sequence benchmark and a binding node constraint; furthermore, by comparing the start and end stages and finding the binding node, it identifies stage direction reversals and missing cross-stage binding, avoiding misjudgments of text compliance based solely on keyword presence; finally, it locates abnormal paragraphs and corresponding entity relationship edges, forming text review results with relationship-level evidence; therefore, this invention improves the logical consistency, anomaly location accuracy, and review efficiency of the pre-entry review of power research project texts. Attached Figure Description

[0009] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Wherein: Figure 1 This is a flowchart illustrating the text review method based on entity relationship verification as shown in this invention. Detailed Implementation

[0010] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.

[0011] Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without inventive effort should fall within the scope of protection of this invention.

[0012] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0013] The following section details a specific implementation method for text review based on entity relationship verification, using the scenario of verifying the consistency of entity relationships in cross-stage materials of power technology projects. The implementation method is illustrated using the scenario of reviewing the completion and acceptance materials of power technology projects in power grid enterprises as an example. The review objects are the project application, task book, results summary materials, test verification materials, and acceptance opinion materials of the same project, after being formatted and consolidated. The review text includes chapter titles, paragraph text, table text transcription, attachment descriptions, and page numbers. Project stages include the project initiation stage, task stage, results stage, and acceptance stage. The review objects include the entity relationship direction between technical issues, research tasks, technical routes, assessment indicators, results names, supporting materials, acceptance indicators, acceptance opinions, and acceptance conclusions.

[0014] In a preferred embodiment, the project name in the text to be reviewed adopts the format of research object + technical objective + research theme; the project number adopts the format of year code + project category code + sequential code; and the undertaking unit adopts the format of the full name of the legally registered unit. The text to be reviewed contains 5 first-level headings, 16 second-level headings, and 46 body paragraphs. Among them, paragraphs 3 to 10 contain content related to project background, research objectives, and technical issues; paragraphs 11 to 24 contain content related to research content, technical route, task division, and assessment indicators; paragraphs 25 to 36 contain content related to research results, result form, intellectual property rights, and test reports; and paragraphs 37 to 46 contain content related to testing and verification, indicator completion status, acceptance opinions, and acceptance conclusions.

[0015] According to an embodiment of the present invention, in combination Figure 1 The flowchart shown illustrates a text review method based on entity relationship verification, which specifically includes the following steps: S1. Divide the text to be reviewed into project phases, and extract the phase entities, task entities, deliverable entities, and acceptance entities from the text to be reviewed, forming entity relationship edges with phase positions. Note that the following should be noted in this step: S1.1 Divide the texts to be reviewed into project initiation stage texts, task stage texts, deliverable stage texts, and acceptance stage texts according to chapter titles and paragraph order, and assign stage positions to the project initiation stage texts, task stage texts, deliverable stage texts, and acceptance stage texts respectively.

[0016] The documents to be reviewed are divided into four stages: project initiation, task completion, deliverables, and acceptance. Determine the heading nodes based on the chapter heading level of the text to be reviewed, and determine the paragraph belonging scope according to the arrangement order of the heading nodes; Paragraphs containing project background, research objectives, justification for project approval, or technical issues in the title node are classified as part of the project approval stage text. Paragraphs whose title nodes contain research content, technical routes, task divisions, or assessment indicators are classified as task phase texts. The paragraphs in the title node that contain research results, result formats, intellectual property rights, papers, standards, or technical reports are classified as result-stage texts. Paragraphs in the title node that contain test verification, indicator completion status, acceptance opinions, or acceptance conclusions are classified as acceptance phase text.

[0017] S1.2 In the project initiation text, task text, deliverable text and acceptance text, extract the stage entity, task entity, deliverable entity and acceptance entity according to the entity boundary, and retain the paragraph number where the stage entity, task entity, deliverable entity and acceptance entity are located.

[0018] Based on entity boundaries, extract phase entities, task entities, deliverable entities, and acceptance entities, including: In the project initiation document, the project name, project number, undertaking unit, research object and technical problem are identified as the stage entities; In the mission phase text, the research task, technical route, task division, assessment indicators and test subjects are defined as mission entities; In the deliverables document, the deliverable name, deliverable type, deliverable ownership, supporting documentation, and completion status are defined as deliverable entities; In the acceptance phase document, the acceptance indicators, test materials, acceptance opinions, acceptance conclusions, and rectification of problems are defined as the acceptance entities; Merge entities with the same name, abbreviations that correspond to the full name, or numbering information in texts from different project phases into a single entity.

[0019] S1.3. Based on the relational predicates in the same paragraph and adjacent paragraphs, determine the relationship types and the start and end order of the relationships between the stage entities, task entities, result entities and acceptance entities, and obtain the entity relationship combination.

[0020] S1.4. Bind the entity relationship group with the stage position and paragraph number to form an entity relationship edge with the stage position.

[0021] Specifically, the text review system first performs layout cleanup on the text to be reviewed, removing consecutive spaces, headers and footers, page numbers, duplicate rows in the table of contents, and table border symbols. For transcribed table text, each table title, header name, and cell content is converted into consecutive paragraphs according to the original row and column order, and the transcribed paragraphs are incorporated into the paragraph scope of their respective chapter titles. After cleanup, the text review system divides the text to be reviewed into stages according to the chapter title hierarchy and paragraph order, so that subsequent entity extraction and entity relationship direction verification have clear project stage boundaries.

[0022] In a preferred embodiment, the stage positions include stage name, stage number, stage start title, stage end title, stage start paragraph number, stage end paragraph number, preceding project stage, and following project stage; the stage numbers are configured as 1, 2, 3, and 4 for the project initiation stage, task stage, deliverable stage, and acceptance stage, respectively; the stage positions in the project initiation stage text include stage name (project initiation stage), stage number 1, stage start title "1 Project Background", stage end title "2 Research Objectives and Technical Issues", stage start paragraph number 3, and stage end paragraph number 10; the stage positions in the task stage text include stage name (task stage), stage number 2, stage start... The title is “3 Research Content and Technical Route”, the end title is “3.4 Assessment Indicators”, the starting paragraph number is 11, and the ending paragraph number is 24. The stage position of the deliverables stage text includes the stage name (deliverables stage), stage number 3, the starting title “4 Research Results and Supporting Materials”, the end title “4.5 Software Test Report”, the starting paragraph number is 25, and the ending paragraph number is 36. The stage position of the acceptance stage text includes the stage name (acceptance stage), stage number 4, the starting title “5 Testing Verification and Acceptance Opinions”, the end title “5.3 Acceptance Conclusion”, the starting paragraph number is 37, and the ending paragraph number is 46.

[0023] In a preferred embodiment, a title node is composed of a title level, a title number, title text, the paragraph number where the title is located, a parent title, and a subordinate title. The text review system identifies lines whose paragraphs begin with consecutive numbers and whose body text length does not exceed 40 Chinese characters as candidate title lines. The consecutive numbers include 1, 1.1, I, (I), and Chapter 1. When a candidate title line is followed by a body text paragraph and the candidate title line is an independent line in the layout, the candidate title line is identified as a title node. For “3 Research Content and Technical Route” in the text to be reviewed, its title level is a first-level title, its title number is 3, its title text is research content and technical route, and its paragraph number is 11. For “3.4 Assessment Indicators”, its title level is a second-level title, its title number is 3.4, its title text is assessment indicators, its paragraph number is 22, and its parent title is “3 Research Content and Technical Route”.

[0024] Preferably, the above-mentioned method of determining the title node can distinguish between ordinary numbering and chapter titles appearing in the main text, reducing errors in project phase division.

[0025] In a preferred embodiment, the paragraph attribution scope consists of the attribution title node, the starting paragraph number, the ending paragraph number, and the attribution paragraph set; the text review system determines the paragraph attribution scope for each title node according to the arrangement order of the title nodes in the text to be reviewed; the body paragraphs between the current title node and the next same-level title node are all assigned to the current title node, and the lower-level title nodes below the current title node and their body paragraphs are all assigned to the current title node, until the next same-level title node or a higher-level title node appears.

[0026] Taking the research content and technical route as an example, the paragraphs within this section are paragraphs 11 to 24. Specifically, 3.1 Research Tasks, 3.2 Technical Route, 3.3 Task Division, and 3.4 Assessment Indicators all fall within this paragraph's scope. The text review system further categorizes paragraphs 3 to 10 as the project initiation stage text based on the project background, research objectives, project justification, and technical issues in the title nodes. Based on the research content, technical route, task division, and assessment indicators, paragraphs 11 to 24 are categorized as the task stage text. Based on research results, result formats, intellectual property rights, papers, standards, and technical reports, paragraphs 25 to 36 are categorized as the result stage text. Finally, based on testing and verification, indicator completion status, acceptance opinions, and acceptance conclusions, paragraphs 37 to 46 are categorized as the acceptance stage text.

[0027] In a preferred embodiment, when the text review system extracts entities from the project initiation stage text, task stage text, deliverable stage text, and acceptance stage text, it identifies them according to the entity boundaries in the project management materials. Entity boundaries include project name boundaries, number boundaries, unit name boundaries, task name boundaries, indicator name boundaries, deliverable name boundaries, material name boundaries, and conclusion statement boundaries. For the project initiation stage text, the text review system extracts the project name text from the project name item as the project name, the number text from the project number item as the project number, the full name of the unit from the undertaking unit item as the undertaking unit, "high proportion of new energy access to the distribution network" as the research object, and "new energy output fluctuations leading to voltage exceeding limits on the distribution side" as a technical problem. All of the above entities belong to the stage entities. For the task stage text, the text review system extracts "dynamic reactive power regulation strategy research" as the research task, "coordinated control route based on transformer voltage measurement and inverter reactive power regulation" as the technical route, and "the algorithm group is responsible for voltage exceeding limit identification, and the equipment group is responsible for inverter communication transformation" as the task division, and extracts "..." as the research object. "Voltage deviation in the distribution area is no more than 3%" is extracted as the assessment indicator, and "distribution distribution area and string inverter" is extracted as the test object; all of the above entities belong to the task entities; for the deliverables, the text review system extracts "distribution side voltage adaptive control software" as the deliverable name, "computer software" as the deliverable type, the number text in the project number field as the deliverable attribution, the number text in the software test report number field as the supporting material, and "completed" as the completion status; all of the above entities belong to the deliverable entities; for the acceptance stage text, the document... This review system extracts "voltage deviation in the distribution area is no more than 3%" as an acceptance indicator, extracts the numbered text from the third-party test report number as test material, extracts "the delivered materials are basically consistent with the assessment indicators in the task book" as acceptance opinion, extracts "passed acceptance" as acceptance conclusion, and extracts "supplementary inverter communication modification instructions" as problem rectification content; all of the above entities belong to the acceptance entities; for entities with the same name, abbreviation corresponding to the full name, or the same numbering information, the text review system merges them into the same entity and retains the paragraph number in the text of each project stage.

[0028] In a preferred embodiment, the text review system determines the relationship type and the order of the relationship based on relational predicates in the same paragraph and adjacent paragraphs. Relational predicates include: originating from, decomposing into, corresponding to, undertaking, supporting, forming, belonging to, proving, satisfying after testing, confirming, passing acceptance, and requiring rectification. When relational predicates are located in the same paragraph and the paragraph contains two or more entities, the text review system determines the initial entity pair according to the order of the entities on both sides of the relational predicate within the paragraph. When relational predicates are located in adjacent paragraphs, and the latter paragraph uses "the aforementioned task, the result, the indicator" as its reference content, the text review system combines the end entity of the former paragraph with the first entity of the latter paragraph to form the initial entity pair. The relationship types include task acceptance, result support, acceptance confirmation, material proof, and rectification association. Among them, when the technical problem and the research task contain "decomposed into" or "correspond to", the relationship type is task acceptance; when the research task and the result name contain "formed" or "supported", the relationship type is result support; when the result name, supporting materials, or acceptance indicators and the acceptance opinions or acceptance conclusions contain "satisfied by testing", "confirmed", or "passed acceptance", the relationship type is acceptance confirmation; when the result name and supporting materials contain "proved" or "belongs to", the relationship type is material proof; when the acceptance opinions and the problem rectification content contain "requires rectification" or "supplementary explanation", the relationship type is rectification association.

[0029] In a preferred embodiment, the relationship sequence consists of a starting entity, an ending entity, a starting stage, and an ending stage. For task acceptance relationships, the text review system uses the stage entity in the preceding project stage as the starting entity and the task entity in the subsequent project stage as the ending entity. For deliverable support relationships, the text review system uses the task entity as the starting entity and the deliverable entity as the ending entity. For acceptance confirmation relationships, the text review system uses either the deliverable entity or the task entity as the starting entity and the acceptance entity as the ending entity. For material verification relationships, the text review system uses the deliverable entity as the starting entity and the supporting materials as the ending entity. For rectification-related relationships, the text review system uses the acceptance entity as the starting entity and the rectification content as the ending entity.

[0030] Taking paragraph 9, "Fluctuations in renewable energy output leading to voltage exceeding limits on the distribution side," as the stage entity and paragraph 13, "Research on dynamic reactive power regulation strategy," as the task entity, when the predicate "decompose into" appears between the two, the text review system obtains the entity relationship combination "Fluctuations in renewable energy output leading to voltage exceeding limits on the distribution side - Task acceptance - Research on dynamic reactive power regulation strategy." The starting stage of the relationship is the project initiation stage, and the ending stage is the task stage. Taking paragraph 14, "Research on dynamic reactive power regulation strategy," and paragraph 28, "Distribution side voltage adaptive control software," as examples, when the predicate "form" appears between the two, the text review system obtains the entity relationship combination "Research on dynamic reactive power regulation strategy - Results support - Distribution side voltage adaptive control software." The starting stage of the relationship is the task stage, and the ending stage is the results stage.

[0031] In a preferred embodiment, the text review system binds entity relationship combinations with stage positions and paragraph numbers to form entity relationship edges with stage positions. Each entity relationship edge includes at least an edge start point, an edge end point, a relationship type, a relationship start point stage, a relationship end point stage, a relationship start point stage number, a relationship end point stage number, a relationship start point paragraph number, a relationship end point paragraph number, a relationship predicate, and the title of the chapter it belongs to. Taking the entity relationship combination formed by paragraphs 14 and 28 as an example, the edge start point of the entity relationship edge is "Research on Dynamic Reactive Power Regulation Strategy", the edge end point is "Distribution Side Voltage Adaptive Control Software", the relationship type is achievement support, the relationship start point stage is the task stage, the relationship end point stage is the achievement stage, the relationship start point stage number is 2, the relationship end point stage number is 3, the relationship start point paragraph number is 14, the relationship end point paragraph number is 28, the relationship predicate is "formation", and the title of the chapter it belongs to includes "3.1 Research Task" and "4.1 Research Achievement".

[0032] It should be noted that step S1, by converting the natural language descriptions in the power technology project materials into entity relationship edges with project stage boundaries, paragraph positions, and relationship directions, solves the technical problems of unclear entity sources, unclear relationship start and end points, and difficulty in paragraph positioning in cross-chapter and cross-stage texts. By binding stage positions, paragraph numbers, and entity relationship combinations, the text review system can shift from text-level content comparison to structured entity relationship direction verification, reducing misjudgments caused by results with the same name, similar indicators, and cross-paragraph backreferences, making anomaly location clearer and stage succession relationships more stable.

[0033] S2. Based on the project phase sequence, entity type, and relationship type, establish a phase relationship direction table including the receiving nodes, and match standard directional relationships in the phase relationship direction table according to the entity type and relationship type of the entity relationship edge. Note that the following should be noted in this step: S2.1 Establish a project phase sequence chain according to the order of project initiation phase, task phase, deliverable phase and acceptance phase; S2.2. Based on the project phase sequence chain, determine the relationship between the entity type of the preceding project phase and the entity type of the subsequent project phase as candidate directional relationships. S2.3. Among the candidate directional relationships, those whose relationship type belongs to task acceptance, result support, or acceptance confirmation are determined as allowed directional relationships; S2.4 For permissible directional relationships where the starting stage and the target stage are not adjacent, the intermediate project stage located between the starting stage and the target stage shall be determined as the receiving node. S2.5. Merge the allowed directional relationships, receiving nodes, and the relationship types corresponding to the allowed directional relationships to form a stage relationship direction table.

[0034] Furthermore, standard directional relationships are matched in the stage relationship direction table, including: The entity relationship edge is split into the entity type of the relationship starting point, the entity type of the relationship ending point, and the relationship type to form a relationship unit to be matched; Find the allowed directional relationships in the stage relationship direction table that are consistent with the entity type of the relationship's starting point, the entity type of the relationship's ending point, and the relationship type; When an allowed directional relationship is found, the preceding stage, the following stage, and the receiving node in the allowed directional relationship are determined as the standard directional relationship; When no allowed directional relationship is found, the entity relationship edge is marked as an entity relationship edge where the standard directional relationship is missing.

[0035] In a preferred embodiment, the project stage sequence chain is arranged in ascending order of stage number, and the chain content is: project initiation stage - task stage - deliverable stage - acceptance stage. Each project stage in the project stage sequence chain has a preceding project stage and a succeeding project stage. Among them, the succeeding project stage of the project initiation stage is the task stage, the preceding project stage of the task stage is the project initiation stage and the succeeding project stage is the deliverable stage, the preceding project stage of the deliverable stage is the task stage and the succeeding project stage is the acceptance stage, and the preceding project stage of the acceptance stage is the deliverable stage. The text review system uses this project stage sequence chain as the basis for judging directional relationships, so that the entity of the project initiation stage cannot point back to the entity of the acceptance stage, and the entity of the acceptance stage cannot interpret the entity of the task stage.

[0036] In a preferred embodiment, the candidate directional relationship consists of a starting stage, a target stage, an entity type at the starting point of the relationship, an entity type at the ending point of the relationship, and a candidate relationship type. The text review system, based on the project stage sequence chain, points the entity types of preceding project stages to the entity types of subsequent project stages to obtain the candidate directional relationship. The candidate directional relationships include: a stage entity in the project initiation stage points to a task entity in the task stage, with the relationship type being task acceptance; a task entity in the task stage points to a result entity in the outcome stage, with the relationship type being outcome support; a result entity in the outcome stage points to an acceptance entity in the acceptance stage, with the relationship type being acceptance confirmation; a stage entity in the project initiation stage points to a result entity in the outcome stage, with the relationship type being outcome support; a task entity in the task stage points to an acceptance entity in the acceptance stage, with the relationship type being acceptance confirmation; a stage entity in the project initiation stage points to an acceptance entity in the acceptance stage, with the relationship type being acceptance confirmation. For material proof relationships and rectification-related relationships within the same project stage, the text review system treats them as auxiliary relationships within the stage and not as standard directional relationships for cross-stage directional consistency review.

[0037] In a preferred embodiment, when the text review system filters for permissible directional relationships from candidate directional relationships, it only retains candidate directional relationships whose relationship type belongs to task acceptance, result support, or acceptance confirmation. Specifically, when the candidate directional relationship is stage entity-task acceptance-task entity, because it represents the decomposition relationship from the project's technical problem to the research task, the text review system determines it as a permissible directional relationship. When the candidate directional relationship is task entity-result support-result entity, because it represents the output relationship from the research task to the result name, result form, or supporting materials, the text review system determines it as a permissible directional relationship. When the candidate directional relationship is result entity-acceptance confirmation-acceptance entity, because it represents the result materials being confirmed by the acceptance opinions or acceptance conclusions after testing and verification, the text review system determines it as a permissible directional relationship. For candidate content such as acceptance entity-result support-result entity or result entity-task acceptance-task entity, which have reversed directions or mismatched relationship types, the text review system does not include them in the permissible directional relationships.

[0038] In a preferred embodiment, for permissible directional relationships where the starting stage and the target stage are not adjacent, the text review system determines the intermediate project stage between the starting stage and the target stage as the receiving node. Specifically, when the starting stage of the permissible directional relationship is the project initiation stage and the target stage is the outcome stage, the intermediate project stage between them is the task stage, and the receiving node is the task entity; when the starting stage of the permissible directional relationship is the task stage and the target stage is the acceptance stage, the intermediate project stage between them is the outcome stage, and the receiving node is the outcome entity; when the starting stage of the permissible directional relationship is the project initiation stage and the target stage is the acceptance stage, the intermediate project stages between them are the task stage and the outcome stage, and the receiving nodes are the task entity and the outcome entity, respectively.

[0039] Taking the technical issue-acceptance confirmation-acceptance conclusion as an example, if the text directly describes "the voltage over-limit caused by the fluctuation of new energy output has passed the acceptance", this relationship spans the task stage and the result stage. The text review system will identify both the task entity and the result entity as the receiving node. Subsequent steps need to find the intermediate entity relationship edge corresponding to the research task and result name between the technical issue and the acceptance conclusion.

[0040] In a preferred embodiment, the stage relationship direction table consists of a direction number, starting stage, target stage, entity type of the relationship's starting point, entity type of the relationship's ending point, relationship type, receiving node, and standard direction description. The text review system merges the allowed directional relationships, receiving nodes, and the relationship types corresponding to the allowed directional relationships to form the stage relationship direction table. Preferably, the stage relationship direction table is configured according to the following table: Table 1. Stage Relationship Direction Table

[0041] In a preferred embodiment, when the text review system matches standard directional relationships in the stage relationship direction table according to the entity type and relationship type of the entity relationship edge, it first splits the entity relationship edge into the entity type of the relationship start point, the entity type of the relationship end point, and the relationship type to form a relationship unit to be matched. The splitting method is as follows: based on the entity category determined in step S1, the entity category corresponding to the edge start point is taken as the entity type of the relationship start point, the entity category corresponding to the edge end point is taken as the entity type of the relationship end point, and the relationship type already bound in the entity relationship edge is taken as the relationship type in the relationship unit to be matched.

[0042] Taking the entity relationship edge “Dynamic Reactive Power Regulation Strategy Research - Results Support - Distribution Side Voltage Adaptive Control Software” as an example, the text review system splits “Dynamic Reactive Power Regulation Strategy Research” into the relationship starting entity type “Task Entity”, splits “Distribution Side Voltage Adaptive Control Software” into the relationship ending entity type “Result Entity”, and takes “Result Support” as the relationship type to obtain the relationship unit to be matched “Task Entity - Result Entity - Result Support”. The relationship unit to be matched is consistent with direction number 2 in the stage relationship direction table. The text review system determines the starting stage “Task Stage”, the target stage “Result Stage”, and the receiving node “Empty” in direction number 2 as the standard direction relationship of this entity relationship edge. If the relationship unit to be matched is “Acceptance Entity - Result Entity - Result Support”, there is no consistent allowed direction relationship in the stage relationship direction table. The text review system marks this entity relationship edge as an entity relationship edge with missing standard direction relationship.

[0043] It should be noted that step S2 solves the technical problems of lacking a unified direction reference and being unable to judge cross-stage transition nodes in natural language review by converting the project management sequence in the cross-stage materials of power technology projects into a comparable stage relationship direction table. Through the combination of project stage sequence chain, allowed direction relationship and transition node, the text review system can distinguish normal relationships between adjacent stages, cross-stage relationships between non-adjacent stages and abnormal relationships that cannot be included in the standard direction, so that the judgment standard of relationship direction is clear and the review basis of transition node is clear.

[0044] S3. Compare the start and end phases of the entity relationship edges with the preceding and following phases in the standard directional relationship, and mark entity relationship edges with opposite start and end phases and those lacking a receiving node. Note that the following should be noted in this step: S3.1 Extract the starting entity, ending entity, starting stage, and ending stage of the relationship from the entity relationship edge to form the directional relationship to be verified; S3.2 Compare the starting stage of the relationship in the direction relationship to be verified with the preceding stage in the standard direction relationship, and compare the ending stage of the relationship in the direction relationship to be verified with the following stage in the standard direction relationship; S3.3 When the starting stage of a relation is the same as the subsequent stage and the ending stage of a relation is the same as the preceding stage, mark the entity relation edge as the entity relation edge with the opposite starting and ending stages; S3.4 When the standard directional relationship includes a receiving node, between the relationship start stage and the relationship end stage, find the intermediate entity relationship edge with the entity in the project stage where the receiving node is located as the edge start or edge end. S3.5 When no intermediate entity relationship edge is found, mark the entity relationship edge as an entity relationship edge that lacks a receiving node.

[0045] Furthermore, the directional relationship to be verified is formed, including: The starting point of the entity relationship edge is taken as the starting entity of the relationship, and the ending point of the entity relationship edge is taken as the ending entity of the relationship. The relationship start stage is determined based on the project stage in which the starting entity of the relationship is located, and the relationship end stage is determined based on the project stage in which the ending entity of the relationship is located. Extract the relationship type and paragraph number of the entity relationship edge, and combine the relationship starting entity, relationship ending entity, relationship starting stage, relationship ending stage, relationship type and paragraph number into the direction relationship to be verified.

[0046] Specifically, the text review system verifies each entity relationship edge formed in step S1 and obtains the standard directional relationship matched in step S2. For entity relationship edges that have been marked as missing standard directional relationships, the text review system no longer performs the judgment of opposite start and end stages and missing connecting nodes, but retains the missing mark and passes it to step S4.

[0047] For example, regarding paragraph 28, "The distribution-side voltage adaptive control software is formed from the research on dynamic reactive power regulation strategies and included in the project deliverables list," and paragraph 14, "The research on dynamic reactive power regulation strategies corresponds to the problem of distribution-side voltage exceeding limits caused by fluctuations in new energy output," the text review system has already formed the entity relationship edge "Research on Dynamic Reactive Power Regulation Strategies - Deliverables Support - Distribution-Side Voltage Adaptive Control Software" in step S1; in step S3, the text review system uses the starting point of the entity relationship edge, "Research on Dynamic Reactive Power Regulation Strategies," as the starting entity of the relationship, and the ending point of the entity relationship edge, "Distribution-Side Voltage Adaptive Control Software," as the ending entity of the relationship; Based on the project stage of the starting entity, the starting stage is determined to be the task stage; based on the project stage of the ending entity, the ending stage is determined to be the outcome stage; then, the relationship type "outcome support" and the paragraph number "paragraph 14, paragraph 28" are extracted from the entity relationship edge, and combined to form the directional relationship to be verified: "Research on dynamic reactive power regulation strategy, distribution side voltage adaptive control software, task stage, outcome stage, outcome support, paragraph 14, paragraph 28"; the preceding stage "task stage" and the following stage "outcome stage" in the directional relationship to be verified are consistent with those in the standard directional relationship, and the text review system does not mark this entity relationship edge as abnormal.

[0048] In a preferred embodiment, for entity relationship edges with opposite start and end stages, the text review system compares them according to the stage name; taking the text "Acceptance conclusion proves that the distribution side voltage adaptive control software has been formed" appearing in paragraph 41 as an example, if step S1 forms the entity relationship edge "Acceptance Conclusion - Acceptance Confirmation - Distribution Side Voltage Adaptive Control Software", its starting entity is "Acceptance Conclusion", the starting stage is the acceptance stage, the ending entity is "Distribution Side Voltage Adaptive Control Software", the ending stage is the result stage, and the relationship type is acceptance confirmation; the standard directional relationship matched in step S2 is "Result". The text review system compares the starting stage "Acceptance Stage" in the directional relationship to be verified with the subsequent stage "Acceptance Stage" in the standard directional relationship, and also compares the ending stage "Result Stage" in the directional relationship to be verified with the preceding stage "Result Stage" in the standard directional relationship. Therefore, it marks the entity relationship edge as an entity relationship edge with opposite start and end stages. This marking indicates that there is a statement in the text to be reviewed that the acceptance conclusion proves the formation of the result, which does not conform to the project stage direction of the result material being formed first and the acceptance conclusion being confirmed later.

[0049] In a preferred embodiment, for entity relationship edges lacking a receiving node, the text review system first determines whether the standard directional relationship contains a receiving node. When the standard directional relationship contains a receiving node, the text review system searches for intermediate entity relationship edges between the relationship's starting and ending stages. Taking the entity relationship edge "New energy output fluctuations cause distribution side voltage exceedance - Acceptance confirmation - Acceptance passed" formed by the technical problem "New energy output fluctuations cause distribution side voltage exceedance - Acceptance confirmation - Acceptance passed" in paragraph 9 and the acceptance conclusion "Acceptance passed" in paragraph 39 as an example, the standard directional relationship matched in step S2 is direction number 6, its preceding stage is the project initiation stage, its following stage is the acceptance stage, and the receiving nodes are the task entity and the result entity. The text review system searches for the task entity between paragraphs 9 and 39. The system identifies intermediate entity relationships where the entity is the starting or ending point of an edge, and also searches for intermediate entity relationships where the result entity is the starting or ending point of an edge. If the text contains "New energy output fluctuations lead to distribution side voltage exceeding limits - Task acceptance - Dynamic reactive power regulation strategy research" and "Dynamic reactive power regulation strategy research - Result support - Distribution side voltage adaptive control software", then the acceptance node is complete, and the text review system does not mark the missing acceptance node. If the text only contains "New energy output fluctuations lead to distribution side voltage exceeding limits - Acceptance confirmation - Pass acceptance", but no intermediate entity relationship edge with the task entity or result entity as the starting or ending point of an edge appears, the text review system marks this entity relationship edge as an entity relationship edge lacking an acceptance node. The missing acceptance nodes are the task entity and the result entity.

[0050] In a preferred embodiment, the text review system's search for intermediate entity relationship edges also includes paragraph position restrictions; when the receiving node is a task entity, the text review system searches for entity relationship edges in the task stage text after the paragraph number of the relationship's starting point and before the paragraph number of the relationship's ending point; when the receiving node is a result entity, the text review system searches for entity relationship edges in the result stage text after the task stage text and before the acceptance stage text; if an entity in the project stage where the receiving node is located appears in the text, but the entity does not form an entity relationship edge with the relationship's starting point entity or relationship's ending point entity, the text review system will still mark the entity relationship edge as an entity relationship edge lacking a receiving node.

[0051] Preferably, this processing method avoids the misconception that the sequence relationship is complete simply because similar nouns appear in the text.

[0052] It should be noted that step S3 solves the technical problem of the difficulty in automatically locating cross-stage logical errors in power technology project materials, such as "reverse proof of acceptance results, inverted interpretation of tasks, and direct jump from project establishment issues to acceptance conclusions," by performing stage direction verification and continuity integrity verification on the entity relationship edges formed in step S1. Through item-by-item comparison between the direction relationship to be verified and the standard direction relationship, the text review system can accurately mark entity relationship edges with opposite start and end stages and missing continuity nodes, making the anomaly type clear, the anomaly edge location accurate, and the cross-stage review process traceable.

[0053] S4. Based on the marking results, determine the paragraphs with abnormal relationship directions and their corresponding entity relationship edges, and generate the text review results. Note that the following should be noted in this step: Specifically, the text review results include the abnormal paragraph number, the corresponding chapter title of the abnormal paragraph, the abnormal type, the abnormal entity relationship edge, the relationship starting entity, the relationship ending entity, the relationship starting stage, the relationship ending stage, the standard directional relationship, the missing connecting node, the relationship type, and the review conclusion. Among them, the abnormal types include reversed starting and ending stages, missing connecting nodes, and missing standard directional relationships. The review conclusion is determined according to the abnormal type, namely, abnormal directional relationship, missing stage connection, missing directional relationship, or approved.

[0054] S4.1 Classify entity relationship edges according to three categories of marking results: opposite start and end stages, missing receiving nodes, and missing standard directional relationships, to obtain opposite direction relationship edges, missing receiving relationship edges, and missing directional relationship edges.

[0055] Specifically, the classification method is as follows: when an entity relationship edge is marked as having opposite start and end stages, the text review system classifies it as an edge with opposite direction; when an entity relationship edge is marked as lacking a successor node, the text review system classifies it as an edge with missing successor node; when an entity relationship edge is marked as lacking a standard directional relationship, the text review system classifies it as an edge with missing directional relationship; if the same entity relationship edge has both the markings of lacking a successor node and lacking a standard directional relationship, the text review system prioritizes classifying it as an edge with missing directional relationship; if the same entity relationship edge has both the markings of opposite start and end stages and lacking a successor node, the text review system prioritizes classifying it as an edge with opposite direction and also lists the missing successor node in the text review results.

[0056] S4.2. Based on the paragraph number of the opposite-direction relationship edge, determine the opposite-direction paragraph, and classify the opposite-direction relationship edge, the relationship start entity, and the relationship end entity into the opposite-direction paragraph.

[0057] Specifically, the method for determining paragraphs with opposite directions is as follows: The text review system obtains the paragraph number of the starting point and the paragraph number of the ending point of the opposite relationship edge, determines the paragraph containing the relationship predicate as the main abnormal paragraph, and determines the paragraph containing the other entity as the association abnormal paragraph; when the starting entity and the ending entity of the relationship are located in the same paragraph, the paragraph is directly determined as the paragraph with opposite directions.

[0058] Taking "Acceptance Conclusion - Acceptance Confirmation - Distribution Side Voltage Adaptive Control Software" as an example, the starting entity "Acceptance Conclusion" is located in paragraph 41, the ending entity "Distribution Side Voltage Adaptive Control Software" is located in paragraph 28, and the predicate "Proof" is located in paragraph 41. The text review system identifies paragraph 41 as the main abnormal paragraph and paragraph 28 as the associated abnormal paragraph. In the paragraphs with opposite directions, the opposite direction relationship edge, the starting entity "Acceptance Conclusion", and the ending entity "Distribution Side Voltage Adaptive Control Software" are included.

[0059] S4.3. Based on the paragraph number of the missing relation edge and the receiving node in the standard directional relation, determine the missing relation paragraph and classify the missing relation edge, the relation start entity, the relation end entity, and the missing receiving node into the missing relation paragraph.

[0060] Specifically, the method for determining the missing continuation paragraph is as follows: The text review system obtains the sequence number of the starting paragraph of the relationship, the sequence number of the ending paragraph of the relationship, and the continuation node in the standard direction relationship, and determines the paragraph containing the cross-stage relationship predicate as the missing continuation paragraph; when both the starting paragraph and the ending paragraph of the relationship contain the cross-stage relationship predicate, both are determined as missing continuation paragraphs.

[0061] Taking the relationship "Fluctuations in renewable energy output leading to voltage exceeding limits on the distribution side - Acceptance confirmation - Passing acceptance" as an example, the starting entity of the relationship is located in paragraph 9, the ending entity of the relationship is located in paragraph 39, the cross-stage relationship predicate "Passing acceptance" is located in paragraph 39, and the receiving nodes in the standard directional relationship are the task entity and the result entity. The text review system identifies paragraph 39 as the missing receiving paragraph and includes the missing receiving relationship edge, the starting entity "Fluctuations in renewable energy output leading to voltage exceeding limits on the distribution side", the ending entity "Passing acceptance", and the missing receiving nodes "task entity, result entity" into the missing receiving paragraph. If the missing receiving node is only the result entity, the text review system lists "the missing receiving node is the result entity" in the missing receiving paragraph and does not extend it to the task entity.

[0062] S4.4. Based on the paragraph number of the missing relation edge in the directional relation, determine the paragraph with the missing directional relation, and classify the missing relation edge, the starting entity of the relation, the ending entity of the relation, and the relation type into the paragraph with the missing directional relation.

[0063] Specifically, the method for determining paragraphs with missing directional relationships is as follows: the text review system obtains the paragraph number of the missing directional relationship edge, identifies the paragraph as a paragraph with missing directional relationship, and categorizes the missing directional relationship edge, the starting entity of the relationship, the ending entity of the relationship, and the relationship type into the paragraph with missing directional relationship.

[0064] Taking the text “Research on Dynamic Reactive Power Adjustment Strategy Related to Rectification of Supporting Materials Corresponding to Software Test Report” appearing in paragraph 32 as an example, if step S1 forms the entity relationship edge “Supporting Materials Corresponding to Software Test Report - Rectification Related - Research on Dynamic Reactive Power Adjustment Strategy”, the entity type of the starting point of the relationship is the result entity, the entity type of the ending point of the relationship is the task entity, and the relationship type is rectification related; if step S2 cannot find a consistent allowed directional relationship in the stage relationship direction table, the text review system will determine paragraph 32 as a paragraph with missing directional relationship, and list the entity of the starting point of the relationship “Supporting Materials Corresponding to Software Test Report”, the entity of the ending point of the relationship “Research on Dynamic Reactive Power Adjustment Strategy”, and the relationship type “Rectification Related” in the result.

[0065] In a preferred embodiment, the review conclusion is determined according to the anomaly type. If the text review result contains an anomaly type with opposite start and end stages, the review conclusion is determined to be an anomaly in directional relationship. If the text review result does not contain an anomaly type with opposite start and end stages but contains an anomaly type with missing connecting nodes, the review conclusion is determined to be a missing stage connection. If the text review result does not contain anomalies with opposite start and end stages and missing connecting nodes but contains an anomaly type with missing standard directional relationships, the review conclusion is determined to be a missing directional relationship. If the text review result does not contain any of the above three anomaly types, the review conclusion is determined to be approved. When the same text to be reviewed contains all three anomaly types, the text review system lists "anomaly in directional relationship, missing stage connection, and missing directional relationship" in the review conclusion, and arranges the results in the order of opposite directional relationship edges, missing connecting relationship edges, and missing directional relationship edges.

[0066] S4.5. Merge paragraphs with opposite directions, paragraphs with missing continuation, paragraphs with missing directional relationships, edges with opposite directions, edges with missing continuation, edges with missing directional relationships, and standard directional relationships to generate the text review result.

[0067] For example, taking the text to be reviewed, formatted with the project name, project number, and undertaking unit as an example, the text review results output by the text review system include the following specific content: Paragraph 41, chapter title "5.2 Acceptance Opinions", anomaly type is reversed start and end stages, anomaly entity relationship edge is "Acceptance Conclusion - Acceptance Confirmation - Distribution Side Voltage Adaptive Control Software", relationship start entity is "Acceptance Conclusion", relationship end entity is "Distribution Side Voltage Adaptive Control Software", relationship start stage is acceptance stage, relationship end stage is result stage, standard directional relationship is "result entity of result stage points to acceptance entity of acceptance stage, relationship type is acceptance confirmation", missing undertaking node is empty, relationship type is acceptance confirmation, review conclusion is directional relationship anomaly; Paragraph 39, chapter title "5.1 Indicator Completion Status", anomaly type is missing undertaking node, anomaly entity relationship edge is "New Energy Output Fluctuation Causes Distribution Side Voltage Exceeding Limit - Acceptance Confirmation - Pass Acceptance", relationship start entity is "New Energy Output Fluctuation Causes Distribution Side Voltage Exceeding Limit", relationship end entity is "Pass Acceptance", relationship start stage is project initiation stage, relationship The final stage is the acceptance stage. The standard directional relationship is "the stage entity of the project initiation stage points to the acceptance entity of the acceptance stage after passing through the task entity and the result entity, and the relationship type is acceptance confirmation". The missing connecting nodes are the task entity and the result entity, and the relationship type is acceptance confirmation. The audit conclusion is missing stage connection. In paragraph 32, the chapter title is "4.4 Supporting Materials". The anomaly type is missing standard directional relationship. The abnormal entity relationship edge is "supporting materials corresponding to the software test report - rectification association - research on dynamic reactive power adjustment strategy". The starting entity of the relationship is "supporting materials corresponding to the software test report". The ending entity of the relationship is "research on dynamic reactive power adjustment strategy". The starting stage of the relationship is the result stage. The ending stage of the relationship is the task stage. The standard directional relationship is empty. The missing connecting node is empty. The relationship type is rectification association. The audit conclusion is missing directional relationship. If the text to be audited only has these three anomalies after verification, paragraphs 41, 39 and 32, the text audit system will determine the overall audit conclusion as "abnormal directional relationship, missing stage connection and missing directional relationship", and output the three abnormal paragraphs, the three abnormal entity relationship edges and the corresponding standard directional relationships.

[0068] Preferably, step S4 converts the marked results formed by the aforementioned direction verification and continuation verification into reviewable text review results, solving the technical problems of abnormal entity relationship edges not being able to be traced back to the original paragraph, review conclusions lacking abnormal type basis, and unclear rectification locations; by classifying by abnormal type, locating by paragraph number, and listing the comparison content according to standard direction relationship, the text review system can directly present abnormal paragraphs, abnormal entity relationship edges, and corresponding standard direction relationships to reviewers, making the review results verifiable, the causes of abnormalities traceable, and the locations of cross-stage material modifications clear.

[0069] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A text review method based on entity relationship verification, characterized in that, include: The text to be reviewed is divided into stages according to the project stage. Stage entities, task entities, deliverable entities and acceptance entities are extracted from the text to be reviewed to form entity relationship edges with stage positions. Based on the project phase sequence, entity type, and relationship type, establish a phase relationship direction table containing receiving nodes, and match standard directional relationships in the phase relationship direction table according to the entity type and relationship type of the entity relationship edge; The relationship start stage and relationship end stage of the entity relationship edge are compared with the preceding stage and following stage in the standard directional relationship, and entity relationship edges with opposite start and end stages and entity relationship edges lacking a receiving node are marked. Based on the marking results, identify paragraphs with abnormal relationship directions and their corresponding entity relationship edges, and generate text review results.

2. The text review method based on entity relationship verification according to claim 1, characterized in that, The formation of the entity relationship edge includes: According to the chapter titles and paragraph order, the text to be reviewed is divided into project initiation stage text, task stage text, deliverable stage text and acceptance stage text, and a stage position is assigned to each of the project initiation stage text, task stage text, deliverable stage text and acceptance stage text respectively; In the project initiation stage text, the task stage text, the result stage text, and the acceptance stage text, stage entities, task entities, result entities, and acceptance entities are extracted according to entity boundaries, and the paragraph numbers of the stage entities, task entities, result entities, and acceptance entities are retained. Based on the relational predicates in the same paragraph and adjacent paragraphs, determine the relationship type and the start and end order of the relationship between the stage entity, the task entity, the result entity and the acceptance entity, and obtain the entity relationship combination; The entity relationship combination is bound to the stage position and the paragraph number to form an entity relationship edge with stage position.

3. The text review method based on entity relationship verification according to claim 2, characterized in that, The process of dividing the texts to be reviewed into project initiation stage texts, task stage texts, deliverable stage texts, and acceptance stage texts includes: The title nodes are determined based on the chapter title level of the text to be reviewed, and the paragraph belonging scope is determined according to the arrangement order of the title nodes; Paragraphs containing project background, research objectives, justification for project approval, or technical issues in the title node are classified as part of the project approval stage text. Paragraphs whose title nodes contain research content, technical routes, task divisions, or assessment indicators are classified as task phase texts. The paragraphs in the title node that contain research results, result formats, intellectual property rights, papers, standards, or technical reports are classified as result-stage texts. Paragraphs in the title node that contain test verification, indicator completion status, acceptance opinions, or acceptance conclusions are classified as acceptance phase text.

4. The text review method based on entity relationship verification according to claim 2, characterized in that, The extraction of stage entities, task entities, result entities, and acceptance entities according to entity boundaries includes: In the project initiation document, the project name, project number, undertaking unit, research object, and technical problem are identified as stage entities; In the aforementioned task phase text, the research task, technical route, task division, assessment indicators, and test subjects are defined as task entities; In the aforementioned deliverables document, the deliverable name, deliverable type, deliverable attribution, supporting documentation, and completion status are defined as deliverable entities; In the aforementioned acceptance phase document, acceptance indicators, test materials, acceptance opinions, acceptance conclusions, and rectification content for problems are defined as acceptance entities; Merge entities with the same name, abbreviations that correspond to the full name, or numbering information in texts from different project phases into a single entity.

5. The text review method based on entity relationship verification according to claim 1, characterized in that, The establishment of the phase relationship direction table containing the receiving nodes includes: Establish a project phase sequence chain according to the order of project initiation, task phase, deliverable phase, and acceptance phase; Based on the project phase sequence chain, the relationship between the entity type of the preceding project phase and the entity type of the subsequent project phase is determined as a candidate directional relationship. Among the candidate directional relationships, those that fall under the categories of task acceptance, result support, or acceptance confirmation are identified as permitted directional relationships. For permissible directional relationships where the starting stage and the target stage are not adjacent, the intermediate project stage located between the starting stage and the target stage is determined as the receiving node. The allowed directional relationships, the receiving nodes, and the relationship types corresponding to the allowed directional relationships are merged to form a stage relationship direction table.

6. The text review method based on entity relationship verification according to claim 5, characterized in that, Matching standard directional relationships in the stage relationship direction table includes: The entity relationship edge is split into the entity type of the relationship starting point, the entity type of the relationship ending point, and the relationship type to form a relationship unit to be matched; Search the stage relationship direction table for allowed directional relationships that match the entity type of the relationship's starting point, the entity type of the relationship's ending point, and the relationship type. When the allowed directional relationship is found, the preceding stage, the following stage, and the receiving node in the allowed directional relationship are determined as the standard directional relationship; When no allowed directional relationship is found, the entity relationship edge is marked as an entity relationship edge with a missing standard directional relationship.

7. The text review method based on entity relationship verification according to claim 1, characterized in that, The relationship start and end stages of the entity relationship edge are compared with the preceding and following stages in the standard directional relationship, including: Extract the starting entity, ending entity, starting stage, and ending stage of the relationship from the entity relationship edge to form the directional relationship to be verified. The starting stage of the relationship in the direction relationship to be verified is compared with the preceding stage in the standard direction relationship, and the ending stage of the relationship in the direction relationship to be verified is compared with the following stage in the standard direction relationship. When the starting stage of the relationship is the same as the subsequent stage and the ending stage of the relationship is the same as the preceding stage, the entity relationship edge is marked as an entity relationship edge with opposite starting and ending stages; When the standard directional relationship includes a receiving node, between the relationship starting stage and the relationship ending stage, find an intermediate entity relationship edge with an entity in the project stage where the receiving node is located as the edge starting point or edge ending point. When the intermediate entity relationship edge is not found, the entity relationship edge is marked as an entity relationship edge that lacks a receiving node.

8. The text review method based on entity relationship verification according to claim 7, characterized in that, The formation of the directional relationship to be verified includes: The starting point of the entity relationship edge is taken as the starting entity of the relationship, and the ending point of the entity relationship edge is taken as the ending entity of the relationship. The relationship start stage is determined based on the project stage in which the relationship start entity is located, and the relationship end stage is determined based on the project stage in which the relationship end entity is located. Extract the relationship type and paragraph number of the entity relationship edge, and combine the relationship starting entity, relationship ending entity, relationship starting stage, relationship ending stage, relationship type and paragraph number into a directional relationship to be verified.

9. The text review method based on entity relationship verification according to claim 1, characterized in that, Generate text review results, including: Based on three categories of labeling results—opposite start and end stages, missing connecting nodes, and missing standard directional relationships—the entity relationship edges are classified into opposite directional relationship edges, missing connecting relationship edges, and missing directional relationship edges. Based on the segment number of the opposite-direction relationship edge, determine the opposite-direction segment, and classify the opposite-direction relationship edge, the relationship start entity, and the relationship end entity into the opposite-direction segment; Based on the segment number of the missing relationship edge and the receiving node in the standard directional relationship, the missing relationship segment is determined, and the missing relationship edge, the relationship start entity, the relationship end entity, and the missing receiving node are assigned to the missing relationship segment. Based on the segment number of the missing directional relation edge, determine the missing directional relation segment, and classify the missing directional relation edge, relation start entity, relation end entity, and relation type into the missing directional relation segment; The text review result is generated by merging the paragraphs with opposite directions, the paragraphs with missing successor relationships, the paragraphs with missing directional relationships, the edges with opposite directions, the edges with missing successor relationships, the edges with missing directional relationships, and the standard directional relationships.

10. The text review method based on entity relationship verification according to claim 9, characterized in that, The text review results include the abnormal paragraph number, the chapter title corresponding to the abnormal paragraph, the abnormal type, the abnormal entity relationship edge, the relationship starting entity, the relationship ending entity, the relationship starting stage, the relationship ending stage, the standard directional relationship, the missing connecting node, the relationship type, and the review conclusion. The anomaly types include reversed start and end phases, missing successor nodes, and missing standard directional relationships; The audit conclusion is determined based on the type of anomaly, namely, abnormal directional relationship, missing stage transition, missing directional relationship, or audit passed.

Images