Patent Application
20220335090
The present disclosure relates generally to term identification systems, and more particularly to identifying equivalent technical terms in different documents using a deep learning model.
Technical terms are commonly used in documents, such as technical articles. Such technical terms may or may not be commonly used among those in the technical field. For example, some technical terms may be said to be “standard” in that the use of such terms are commonly accepted in the technical field. For instance, alternating current, capacitor, diode, etc. are commonly understood terms in the field of electrical engineering. There are times, however, when non-standard technical terms are used in documents. Such non-standard technical terms though may not be commonly accepted in the technical field. For example, an “administrative console” in one document could be referred to as a “web management console” in another document despite referring to the same concept or functionality.
When an individual becomes knowledgeable about a product, including the technical terms used to describe that product, it may be difficult for that individual to understand another product even though it may have similar functionality if different technical terms are used to describe the same functionality. As a result, the individual may have difficulty in understanding or using this new but similar product.
In one embodiment of the present disclosure, a computer-implemented method for identifying equivalent technical terms comprises training a deep learning model to identify equivalent technical terms. The method further comprises applying the deep learning model to a first document. The method additionally comprises analyzing each sentence of the first document to identify technical terms. Furthermore, the method comprises analyzing text surrounding a first technical term identified in the first document to determine a meaning of the text surrounding the first technical term. Additionally, the method comprises reviewing a glossary list to determine if the meaning of the analyzed text surrounding the first technical term in the first document matches a meaning in the glossary list linked to a second technical term, where the glossary list comprises a list of meanings associated with equivalent technical terms in designated products. In addition, the method comprises identifying the second technical term equivalent to the first technical term from the glossary list in response to determining the meaning of the analyzed text surrounding the first technical term matching the meaning in the glossary list linked to the second technical term.
Other forms of the embodiment of the computer-implemented method described above are in a system and in a computer program product.
The foregoing has outlined rather generally the features and technical advantages of one or more embodiments of the present disclosure in order that the detailed description of the present disclosure that follows may be better understood. Additional features and advantages of the present disclosure will be described hereinafter which may form the subject of the claims of the present disclosure.
A better understanding of the present disclosure can be obtained when the following detailed description is considered in conjunction with the following drawings, in which:
As stated in the Background section, technical terms are commonly used in documents, such as technical articles. Such technical terms may or may not be commonly used among those in the technical field. For example, some technical terms may be said to be “standard” in that the use of such terms are commonly accepted in the technical field. For instance, alternating current, capacitor, diode, etc. are commonly understood terms in the field of electrical engineering. There are times, however, when non-standard technical terms are used in documents. Such non-standard technical terms though may not be commonly accepted in the technical field. For example, an “administrative console” in one document could be referred to as a “web management console” in another document despite referring to the same concept or functionality.
When an individual becomes knowledgeable about a product, including the technical terms used to describe that product, it may be difficult for that individual to understand another product even though it may have similar functionality if different technical terms are used to describe the same functionality. As a result, the individual may have difficulty in understanding or using this new but similar product.
Currently, term identification systems simply identify terms in documents, such as performing a search in a document (e.g., electronic document) for the term entered by a user. In some of these term identification systems, such systems may attempt to identify words with similar meanings as the term entered by the user, such as locating words in the documents that are used in the definition of the term entered by the user.
Unfortunately, term identification systems are unable to identify non-standard technical terms used in different documents (e.g., electronic documents) yet have the same meaning. Such an identification would be helpful to the user in achieving a greater understanding of the technology discussed in the document.
The embodiments of the present disclosure provide a means for identifying non-standard technical terms that have the same meaning (such technical terms are said to be “equivalent”) by using a deep learning model trained to identify equivalent technical terms.
In some embodiments of the present disclosure, the present disclosure comprises a computer-implemented method, system and computer program product for identifying equivalent technical terms. In one embodiment of the present disclosure, a deep learning model is trained to identify equivalent technical terms. The deep learning model is then applied to a new document. The sentences of the document are then analyzed to identify technical terms. In one embodiment, natural language processing is used to identify the technical terms by searching the document with terms matching the technical terms listed in a data structure (e.g., list). Text is then analyzed surrounding the technical term identified in the document to determine the meaning of such text. In one embodiment, such meaning may be inferred using part-of-speech tagging or based on a user-designated number of words preceding or succeeding the technical term. A glossary list is then reviewed to determine if the identified meaning of the analyzed text matches a meaning of a concept in the glossary list linked to a technical term. The “glossary list,” as used herein, is a list of meanings/concepts associated with equivalent technical terms in designated products. “Equivalent technical terms,” as used herein, refer to technical terms having the same semantic meaning within a threshold degree. In response to determining that the meaning of the analyzed text matches a meaning/concept in the glossary list linked to an equivalent technical term, the technical term in the document is annotated with the equivalent technical term. For example, if the meaning of the analyzed text is “UI Console” in connection with the technical term of “Web Console” and the glossary list links or associates such a meaning to the technical term of “Dashboard,” then the technical term of “Web Console” may be replaced or tagged with the equivalent term of “Dashboard” so that the user will understand that the non-standard technical term of “Web Console” is the same as the non-standard technical term of “Dashboard.” In this manner, non-standard technical terms used in different documents (e.g., technical articles) to describe different products, but have the same meaning/concept, are able to be identified as being equivalent technical terms thereby allowing greater understanding of the documents.
In the following description, numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure may be practiced without such specific details. In other instances, well-known circuits have been shown in block diagram form in order not to obscure the present disclosure in unnecessary detail. For the most part, details considering timing considerations and the like have been omitted inasmuch as such details are not necessary to obtain a complete understanding of the present disclosure and are within the skills of persons of ordinary skill in the relevant art.
Referring now to the Figures in detail,
A discussion regarding the software components used by technical term identification system 101 to identify equivalent technical terms in documents is discussed below in connection with
System 100 further includes a computing device 103 of a user connected to technical term identification system 101 via a network 104. It is noted that both computing device 103 and the user of computing device 103 may be identified with element number 103.
Computing device 103 may be any type of computing device (e.g., portable computing unit, Personal Digital Assistant (PDA), laptop computer, mobile device, tablet personal computer, smartphone, mobile phone, navigation device, gaming unit, desktop computer system, workstation, Internet appliance and the like) configured with the capability of connecting to network 104 and consequently communicating with technical term identification system 101.
In one embodiment, user 103 may provide technical term identification system 101 with a document (e.g., electronic document) containing technical terms that may need to be annotated with technical terms more familiar to user 103 thereby providing user 103 with a greater understanding of the technology discussed in the document.
Network 104 may be, for example, a local area network, a wide area network, a wireless wide area network, a circuit-switched telephone network, a Global System for Mobile Communications (GSM) network, a Wireless Application Protocol (WAP) network, a WiFi network, an IEEE 802.11 standards network, various combinations thereof, etc. Other networks, whose descriptions are omitted here for brevity, may also be used in conjunction with system 100 of
Furthermore, as illustrated in
System 100 is not to be limited in scope to any one particular network architecture. System 100 may include any number of technical term identification systems 101, repositories 102, 105, computing devices 103 and networks 104.
Referring now to
Referring to
In one embodiment, deep learning engine 202 uses a machine learning algorithm (e.g., supervised learning) to build a mathematical model based on sample data consisting of structured and unstructured data (e.g., documents annotated with technical terms that are identified as being equivalent). Such structured and unstructured data may be obtained and tabulated by experts, who in turn, utilize such information to develop the sample data. Such a data set is referred to herein as the “training data” which is used by the machine learning algorithm of deep learning engine 202 to make predictions or decisions without being explicitly programmed to perform the task. The algorithm iteratively makes predictions on the training data and is corrected by the expert until the predictions achieve the desired accuracy. Examples of such supervised learning algorithms include nearest neighbor, Naïve Bayes, decision trees, linear regression, support vector machines and neural networks.
In one embodiment, technical term identification system 101 includes an annotate engine 203 configured to annotate a document by replacing a technical term with an equivalent technical term identified by deep learning engine 202 using a glossary list as discussed further below. In another embodiment, annotate engine 203 is configured to tag a technical term in the document with the equivalent technical term identified by deep learning engine 202 using the glossary list as discussed further below.
In one embodiment, in connection with training the deep learning model to identify equivalent technical terms, annotate engine 203 of technical term identification system 101 is configured to annotate the terms (technical terms) in the text of the documents with tags. A “tag,” as used herein, refers to a keyword or term, such as a technical term, placed in the location of the annotated term(s). In one embodiment, such tags of technical terms may be identified from a data structure (table) consisting of a list of technical terms (e.g., web management console, web application, Hypertext Markup Language (HTML)) stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102. In one embodiment, annotate engine 203 is configured to utilize natural language processing to search documents with terms matching the technical terms listed in such a data structure. The technical terms in the analyzed documents are then tagged with the matching technical terms.
In one embodiment, annotate engine 203 is further configured to annotate the tagged technical terms with entity types (e.g., person, organization, code, software component, etc.). In one embodiment, such entity types are previously defined from an expert. In one embodiment, after an expert has established a list of entity types, annotate engine 203 utilizes an entity identification engine (e.g., Statistical Information and Relation Extraction (SIRE) engine available from IBM®) to annotate the tagged technical terms with an entity type. By annotating the tagged technical terms with an entity type, it may assist the deep learning model of technical term identification system 101 in identifying equivalent technical terms. For example, technical terms that are annotated with a different entity type are less likely to be deemed to be equivalent technical terms than if they were annotated with the same entity type.
In one embodiment, the SIRE engine provides components for term or entity detection using maximum entropy models that can be trained from annotated data, a trainable co-reference component for grouping detected terms in a document that correspond to the same entity, and a trainable relation extraction system.
In one embodiment, the entity identification engine, such as the SIRE engine, utilized by annotate engine 203 provides a syntactic breakdown of text in a document, identification of entities detected in the text, co-reference resolution (resolution of two or more terms that refer to the same entity), and relationship detection between entities. In addition, logic is provided for generating search indices augmented with the co-referenced terms discovered by the entity identification engine, and for generating a relational database that stores the entities found by the entity identification engine, the entity type, terms related to the entities, the frequency of the particular relationship within a corpus or across corpora, the time of publication of the document that is the source of the relationship, the corpus identifier, and the document identifier of the document that is the source of the relationship.
In one embodiment, technical term identification system 101 includes an analyzer 204 configured to analyze each sentence of the document to identify the technical term(s), if any. In one embodiment, analyzer 204 is configured to utilize natural language processing to search documents with terms matching the technical terms listed in a data structure (e.g., table). If any technical terms listed in the data structure are identified, then such technical terms are identified in the document, such as being tagged as a technical term. In one embodiment, such a data structure is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102.
In one embodiment, analyzer 204 is further configured to analyze text surrounding the identified technical terms in the documents to determine the meaning of such text. In one embodiment, analyzer 204 utilizes natural language processing to identify the meaning in terms of concepts associated with such technical terms. A “concept,” as used herein, refers to an idea or a general notion, such as a deploying web applications. In one embodiment, when the technical term corresponds to a noun, analyzer 204 identifies such concepts based on identifying the technical term-verb-noun pattern using part-of-speech tagging. For example, if the technical term is “web application manager” and the corresponding verb is “deploying” followed by the noun of “web applications,” then the pattern of “web application manager deploying web applications” is identified. The concept of deploying web applications may then be inferred based on the verb-noun pattern describing the technical term.
In one embodiment, part-of-speech tagging is accomplished using a rule-based (e.g., E. Brill's tagger) or a stochastic part-of-speech tagging algorithm (e.g., Hidden Markov Model (HMM)).
In one embodiment, the meaning of a technical term may be inferred based on a user-designated number of words preceding or succeeding the technical term. Such words may be associated with the technical term and stored in a data structure (e.g., table), which is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102. For example, in the sentence “A capacitor is a device that stores electrical energy in an electric field.,” the words “is a device that stores electrical energy” may be identified as succeeding the technical term of “capacitor.” Such words that are nearby the technical term may provide the meaning of the technical term, such as a capacitor is a device that stores electrical energy. Such a meaning may also correspond to the “concept” of the technical term. In one embodiment, such meanings or concepts are stored in a data structure (e.g., table), referred to herein as the “glossary list,” that stores a listing of concepts/meanings and the associated technical terms. In one embodiment, the data structure is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102.
A further description of these and other functions is provided below in connection with the discussion of the method for identifying equivalent technical terms in documents.
Prior to the discussion of the method for identifying equivalent technical terms in documents, a description of the hardware configuration of technical term identification system 101 (
Referring now to
Technical term identification system 101 has a processor 301 connected to various other components by system bus 302. An operating system 303 runs on processor 301 and provides control and coordinates the functions of the various components of
Referring again to
Technical term identification system 101 may further include a communications adapter 309 connected to bus 302. Communications adapter 309 interconnects bus 302 with an outside network (e.g., network 104 of
In one embodiment, application 304 of technical term identification system 101 includes the software components of trainer engine 201, deep learning engine 202, annotate engine 203 and analyzer 204. In one embodiment, such components may be implemented in hardware, where such hardware components would be connected to bus 302. The functions discussed above performed by such components are not generic computer functions. As a result, technical term identification system 101 is a particular machine that is the result of implementing specific, non-generic computer functions.
In one embodiment, the functionality of such software components (e.g., trainer engine 201, deep learning engine 202, annotate engine 203 and analyzer 204) of technical term identification system 101, including the functionality for identifying equivalent technical terms in documents, may be embodied in an application specific integrated circuit.
The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be accomplished as one step, executed concurrently, substantially concurrently, in a partially or wholly temporally overlapping manner, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
As stated above, technical terms are commonly used in documents, such as technical articles. Such technical terms may or may not be commonly used among those in the technical field. For example, some technical terms may be said to be “standard” in that the use of such terms are commonly accepted in the technical field. For instance, alternating current, capacitor, diode, etc. are commonly understood terms in the field of electrical engineering. There are times, however, when non-standard technical terms are used in documents. Such non-standard technical terms may not be commonly accepted terms used in the technical field. For example, an “administrative console” in one document could be referred to as a “web management console” in another document despite referring to the same concept or functionality. When an individual becomes knowledgeable about a product, including the technical terms used to describe that product, it may be difficult for that individual to understand another product even though it may have similar functionality if different technical terms are used to describe the same functionality. As a result, the individual may have difficulty in understanding or using this new but similar product. Currently, term identification systems simply identify terms in documents, such as performing a search in a document (e.g., electronic document) for the term entered by a user. In some of these term identification systems, such systems may attempt to identify words with similar meanings as the term entered by the user, such as locating words in the documents that are used in the definition of the term entered by the user. Unfortunately, term identification systems are unable to identify non-standard technical terms used in different documents (e.g., electronic documents) yet have the same meaning. Such an identification would be helpful to the user in achieving a greater understanding of the technology discussed in the document.
The embodiments of the present disclosure provide a means for identifying non-standard technical terms that have the same meaning (such technical terms are said to be “equivalent”) by using a deep learning model trained to identify equivalent technical terms as discussed below in connection with
As discussed above,
Referring to
Referring to
In one embodiment, trainer engine 201 collects or gathers documents (e.g., electronic documents), such as technical articles, from repository 102 as well as documents that are publicly available on the Internet, such as accessing such documents in repository 105 via network 104. In one embodiment, such documents used for training purposes are populated in repository 102 by an expert. Such documents may then be provided to technical term identification system 101 for training purposes.
In step 502, annotate engine 203 of technical term identification system 101 annotates terms (technical terms) in the text of the documents with tags. A “tag,” as used herein, refers to a keyword or term, such as a technical term, placed in the location of the annotated term(s). As discussed above, in one embodiment, such tags of technical terms may be identified from a data structure (table) consisting of a list of technical terms (e.g., web management console, web application, Hypertext Markup Language (HTML)) stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102. In one embodiment, annotate engine 203 is configured to utilize natural language processing to search documents with terms matching the technical terms listed in such a data structure. The technical terms in the analyzed documents are then tagged with the matching technical terms.
In one embodiment, annotate engine 203 further annotates the tagged technical terms with entity types (e.g., person, organization, code, software component, etc.). In one embodiment, such entity types are previously defined from an expert. In one embodiment, after an expert has established a list of entity types, annotate engine 203 utilizes an entity identification engine (e.g., Statistical Information and Relation Extraction (SIRE) engine available from IBM®) to annotate the tagged technical terms with an entity type. By annotating the tagged technical terms with an entity type, it may assist the deep learning model of technical term identification system 101 in identifying equivalent technical terms. For example, technical terms that are annotated with a different entity type are less likely to be deemed to be equivalent technical terms than if they were annotated with the same entity type.
In one embodiment, the SIRE engine provides components for term or entity detection using maximum entropy models that can be trained from annotated data, a trainable co-reference component for grouping detected terms in a document that correspond to the same entity, and a trainable relation extraction system.
In one embodiment, the entity identification engine, such as the SIRE engine, utilized by annotate engine 203 provides a syntactic breakdown of text in a document, identification of entities detected in the text, co-reference resolution (resolution of two or more terms that refer to the same entity), and relationship detection between entities. In addition, logic is provided for generating search indices augmented with the co-referenced terms discovered by the entity identification engine, and for generating a relational database that stores the entities found by the entity identification engine, the entity type, terms related to the entities, the frequency of the particular relationship within a corpus or across corpora, the time of publication of the document that is the source of the relationship, the corpus identifier, and the document identifier of the document that is the source of the relationship.
An example of annotate engine 203 annotating the technical terms in the text of the documents with tags is shown in
Referring to
As previously discussed, such tags of technical terms may be identified from a data structure (table) consisting of a list of technical terms. In one embodiment, annotate engine 203 utilizes natural language processing to search documents (601, 602) with terms matching the technical terms listed in such a data structure. Such matching terms are tagged with the matching technical term, such as tags 603, 604, 605, 606 and 607.
Returning to
In one embodiment, the user of computing device 103 may obtain access of the documents (e.g., documents 601, 602) from technical term identification system 101 and annotate the documents using a software tool, such as ClickUp®, Filestage®, Prodigy®, Annotate, PDF Annotator®, Drawboard® Projects, Doccano, Ink2Go, etc.
Such annotations may be provided to technical term identification system 101 by the user of computing device 103 via network 104, such as shown in
Referring to
Returning to
As discussed above, in one embodiment, analyzer 204 utilizes natural language processing to identify the meaning in terms of concepts associated with such technical terms. A “concept,” as used herein, refers to an idea or a general notion, such as a deploying web applications. In one embodiment, when the technical term corresponds to a noun, analyzer 204 identifies such concepts based on identifying the technical term-verb-noun pattern using part-of-speech tagging. For example, if the technical term is “web application manager” and the corresponding verb is “deploying” followed by the noun of “web applications,” then the pattern of “web application manager deploying web applications” is identified. The concept of deploying web applications may then be inferred based on the verb-noun pattern describing the technical term.
In one embodiment, part-of-speech tagging is accomplished using a rule-based (e.g., E. Brill's tagger) or a stochastic part-of-speech tagging algorithm (e.g., Hidden Markov Model (HMM)).
In one embodiment, the meaning of a technical term may be inferred based on a user-designated number of words preceding or succeeding the technical term. Such words may be associated with the technical term and stored in a data structure (e.g., table), which is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102. For example, in the sentence “A capacitor is a device that stores electrical energy in an electric field.,” the words “is a device that stores electrical energy” may be identified as succeeding the technical term of “capacitor.” Such words that are nearby the technical term may provide the meaning of the technical term, such as a capacitor is a device that stores electrical energy. Such a meaning may also correspond to the “concept” of the technical term. In one embodiment, such meanings or concepts are stored in a data structure (e.g., table), referred to herein as the “glossary list,” that stores a listing of concepts/meanings and the associated technical terms. In one embodiment, the data structure is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102.
In step 505, analyzer 204 of technical term identification system 101 identifies a technical term in the first document (e.g., document 601) with a same meaning as another technical term in the second document (e.g., document 602).
In one embodiment, the technical term in the first document is deemed to have the same meaning as another technical term in the second document when the meaning of the analyzed text surrounding the technical term in the first document has a semantic similarity to the meaning of the analyzed text surrounding the technical term in the second document that exceeds a threshold value.
As discussed above, a “glossary list” may store technical terms and their associated meanings/concepts. For example, referring to
Continuing to refer to
Upon identifying the same meaning/concept being expressed in the other document (e.g., document 602), analyzer 204 analyzes the text of the second document for the technical term, which may be a non-standard technical term, that is associated with the matching meaning/concept. Such a technical term may be found using natural language processing by identifying the subject of the paragraph containing the matching meaning/concept. For example, referring to the
As shown in
By identifying matching meanings in documents 601, 602, analyzer 204 is able to determine that the technical term of administrative control 605 corresponds to the technical term of web application manager 610. As a result, in one embodiment, annotate engine 203 annotates document 602 by including the tag of administrative console 611 with the technical term of web application manager 610 to indicate that they are equivalent technical terms.
In step 506, technical term identification system 101 adds the equivalent terms to the glossary list, including the documents or the products discussed in the documents, as well as the meaning/concept. The “glossary list,” as used herein, is a list of meanings/concepts associated with equivalent technical terms in designated products. “Equivalent technical terms,” as used herein, refer to technical terms having the same semantic meaning within a threshold degree.
The deep learning model continues to be trained until an expert determines that the results are satisfactory, such as automatically identifying equivalent terms using the glossary list without having a user to provide annotations to the technical terms in order to identify equivalent technical terms. For instance, referring to the above example, after analyzer 204 determines that the meaning of “administrative console” in document 601 matches the meaning of “web application manager” in document 602, and such terms were previously identified as being equivalent technical terms in the glossary list, then the deep learning model would simply annotate such terms as being equivalent technical terms (e.g., annotate “administrative console” with the tag of “web application manager” in document 601 and annotate “web application manager” with the tag of “administrative console” in document 602) without having to add such terms to the glossary list.
An exemplary glossary list as a result of training the deep learning model is shown in
As shown in
Returning now to
In step 403, analyzer 204 of technical term identification system 101 analyzes each sentence of the document to identify any technical terms. As previously discussed, in one embodiment, analyzer 204 is configured to utilize natural language processing to search documents with terms matching the technical terms listed in a data structure (e.g., list containing a listing of technical terms). If any technical terms listed in the data structure are identified, then such technical terms are identified in the document, such as being tagged as a technical term. In one embodiment, such a data structure is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102.
In step 404, analyzer 204 of technical term identification system 101 analyzes the text surrounding the identified technical term in the document to determine the meaning of such text. As discussed above, in one embodiment, analyzer 204 is configured to utilize natural language processing to search documents with terms matching the technical terms listed in a data structure (e.g., list containing a listing of technical terms). If any technical terms listed in the data structure are identified, then such technical terms are identified in the document, such as being tagged as a technical term. In one embodiment, such a data structure is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102.
In one embodiment, analyzer 204 is further configured to analyze text surrounding the identified technical terms in the documents to determine the meaning of such text. In one embodiment, analyzer 204 utilizes natural language processing to identify the meaning in terms of concepts associated with such technical terms. A “concept,” as used herein, refers to an idea or a general notion, such as a deploying web applications. In one embodiment, when the technical term corresponds to a noun, analyzer 204 identifies such concepts based on identifying the technical term-verb-noun pattern using part-of-speech tagging. For example, if the technical term is “web application manager” and the corresponding verb is “deploying” followed by the noun of “web applications,” then the pattern of “web application manager deploying web applications” is identified. The concept of deploying web applications may then be inferred based on the verb-noun pattern describing the technical term.
In one embodiment, part-of-speech tagging is accomplished using a rule-based (e.g., E. Brill's tagger) or a stochastic part-of-speech tagging algorithm (e.g., Hidden Markov Model (HMM)).
In one embodiment, the meaning of a technical term may be inferred based on a user-designated number of words preceding or succeeding the technical term. Such words may be associated with the technical term and stored in a data structure (e.g., table), which is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102. For example, in the sentence “A capacitor is a device that stores electrical energy in an electric field.,” the words “is a device that stores electrical energy” may be identified as succeeding the technical term of “capacitor.” Such words that are nearby the technical term may provide the meaning of the technical term, such as a capacitor is a device that stores electrical energy. Such a meaning may also correspond to the “concept” of the technical term. In one embodiment, such meanings or concepts are stored in a data structure (e.g., table), referred to herein as the “glossary list,” that stores a listing of concepts/meanings and the associated technical terms. In one embodiment, the data structure is stored in a storage device (e.g., memory, disk drive) of technical term identification system 101 or in repository 102.
In step 405, technical term identification system 101 (deep learning model of technical term identification system 101) reviews glossary list 700 to determine if the meaning of the analyzed text matches a meaning/concept in glossary list 700 linked to a technical term. For example, if the meaning of the analyzed text is “UI Console,” then technical term identification system 101 may identify such meaning/concept in glossary list 700 that is linked or associated with the technical terms of “Web Console” or “Dashboard.” If the technical term of “Web Console” is used in the document being reviewed, then the technical term of “Web Console” may be replaced or tagged with the equivalent term of “Dashboard” so that the user will understand that the non-standard technical term of “Web Console” is the same as the non-standard technical term of “Dashboard.”
In one embodiment, the meaning of the analyzed text surrounding the technical term in the analyzed document is deemed to match a meaning/concept in glossary list 700 when the meaning of the analyzed text surrounding the technical term has a semantic similarity to a meaning in glossary list 700 that exceeds a threshold value, which may be user-specified.
In step 406, technical term identification system 101 (deep learning model of technical term identification system 101) determines whether there is a match of the identified meaning of the analyzed text with a meaning/concept in glossary list 700 linked to a technical term.
If there was not a match of the identified meaning of the analyzed text with a meaning/concept in glossary list 700 linked to a technical term, then, in step 407, technical term identification system 101 (deep learning model of technical term identification system 101) did not identify equivalent technical terms.
If, however, there was a match of the identified meaning of the analyzed text with a meaning/concept in glossary list 700 linked to a technical term, then, in step 408, technical term identification system 101 (deep learning model of technical term identification system 101) identifies equivalent technical terms.
In step 409, annotate engine 203 of technical term identification system 101 annotates the document, such as by replacing the technical term in the document with the equivalent technical term found in glossary list 700 or tagging the technical term in the document with the equivalent technical term found in glossary list 700.
In this manner, the principles of the present disclosure enable term identification systems to identify non-standard technical terms that have the same meaning as other non-standard technical terms being used in a document using a deep learning model trained to identify equivalent technical terms. Consequently, technical terms used in a document may be replaced or tagged with equivalent technical terms that may be more familiar to the reviewer of the document.
As a result, a user, such as a technical user, will be able to understand and master another product by reviewing the description of that product with technical terms familiar to that technical user. Furthermore, such a technical user will be able to more quickly troubleshoot issues since the document used to troubleshoot issues will contain terms familiar to that technical user. Additionally, the technical user will be able to more effectively compare products since the user will obtain a better understanding of the products due to the documents describing such products containing technical terms that may be more familiar to the user. Furthermore, by identifying equivalent technical terms, the product architecture and technical systems will be better understood resulting in making more informed business decisions.
Furthermore, the present disclosure improves the technology or technical field involving term identification systems. As discussed above, technical terms are commonly used in documents, such as technical articles. Such technical terms may or may not be commonly used among those in the technical field. For example, some technical terms may be said to be “standard” in that the use of such terms are commonly accepted in the technical field. For instance, alternating current, capacitor, diode, etc. are commonly understood terms in the field of electrical engineering. There are times, however, when non-standard technical terms are used in documents. Such non-standard technical terms though may not be commonly accepted in the technical field. For example, an “administrative console” in one document could be referred to as a “web management console” in another document despite referring to the same concept or functionality. When an individual becomes knowledgeable about a product, including the technical terms used to describe that product, it may be difficult for that individual to understand another product even though it may have similar functionality if different technical terms are used to describe the same functionality. As a result, the individual may have difficulty in understanding or using this new but similar product. Currently, term identification systems simply identify terms in documents, such as performing a search in a document (e.g., electronic document) for the term entered by a user. In some of these term identification systems, such systems may attempt to identify words with similar meanings as the term entered by the user, such as locating words in the documents that are used in the definition of the term entered by the user. Unfortunately, term identification systems are unable to identify non-standard technical terms used in different documents (e.g., electronic documents) yet have the same meaning. Such an identification would be helpful to the user in achieving a greater understanding of the technology discussed in the document.
Embodiments of the present disclosure improve such technology by training a deep learning model to identify equivalent technical terms. The deep learning model is then applied to a new document. The sentences of the document are then analyzed to identify technical terms. In one embodiment, natural language processing is used to identify the technical terms by searching the document with terms matching the technical terms listed in a data structure (e.g., list). Text is then analyzed surrounding the technical term identified in the document to determine the meaning of such text. In one embodiment, such meaning may be inferred using part-of-speech tagging or based on a user-designated number of words preceding or succeeding the technical term. A glossary list is then reviewed to determine if the identified meaning of the analyzed text matches a meaning of a concept in the glossary list linked to a technical term. The “glossary list,” as used herein, is a list of meanings/concepts associated with equivalent technical terms in designated products. “Equivalent technical terms,” as used herein, refer to technical terms having the same semantic meaning within a threshold degree. In response to determining that the meaning of the analyzed text matches a meaning/concept in the glossary list linked to an equivalent technical term, the technical term in the document is annotated with the equivalent technical term. For example, if the meaning of the analyzed text is “UI Console” in connection with the technical term of “Web Console” and the glossary list links or associates such a meaning to the technical term of “Dashboard,” then the technical term of “Web Console” may be replaced or tagged with the equivalent term of “Dashboard” so that the user will understand that the non-standard technical term of “Web Console” is the same as the non-standard technical term of “Dashboard.” In this manner, non-standard technical terms used in different documents (e.g., technical articles) to describe different products, but have the same meaning/concept, are able to be identified as being equivalent technical terms thereby allowing greater understanding of the documents. Furthermore, in this manner, there is an improvement in the technical field involving term identification systems.
The technical solution provided by the present disclosure cannot be performed in the human mind or by a human using a pen and paper. That is, the technical solution provided by the present disclosure could not be accomplished in the human mind or by a human using a pen and paper in any reasonable amount of time and with any reasonable expectation of accuracy without the use of a computer.
The descriptions of the various embodiments of the present disclosure have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
