Information processing apparatus and program

Abstract

To improve identification accuracy.SOLUTION: The server device 2 includes an acquisition unit 31 that acquires first information such as a name related to a first organization and second information such as a name related to a second organization different from the first organization, a determination unit 32 that determines the presence or absence of a relationship such as business card exchange between the first organization and the second organization based on the first information and the second information, and an identification unit 33 that identifies at least one of the first organization and the second organization based on a result of the determination of the presence or absence of the relationship by the determination unit 32.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device and a program. [Background technology]

[0002] For example, identification is performed for companies for name identification purposes.

[0003] For example, Patent Document 1 describes matching using names and addresses. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-348489 Summary of the Invention [Problem to be solved by the invention]

[0005] However, when identifying a company by its name, etc., there is a possibility that there may be multiple companies with the same name, and therefore there is room for improvement in the identification accuracy.

[0006] In view of the above-described problems, an object of the present disclosure is to provide an information processing device and a program that can improve identification accuracy. [Means for solving the problem]

[0007] In order to solve the above problem, an information processing device according to a first aspect of the present disclosure includes an acquisition unit that acquires first information about a first organization and second information about a second organization different from the first organization, a determination unit that determines whether or not there is a relationship between the first organization and the second organization based on the first information and the second information, and an identification unit that identifies at least one of the first organization and the second organization based on the result of the determination.

[0008] In addition, in the information processing device according to the second aspect of the present disclosure, in the first aspect, the determination unit determines that a relationship exists between the first organization and the second organization if there is a history of exchange between the first organization and the second organization.

[0009] Furthermore, in the information processing device according to the third aspect of the present disclosure, in the first or second aspect, the determination unit refers to a database in which combinations of organizations that are related to each other are registered, and determines whether or not the combination of organizations corresponding to the first organization and the second organization exists in the database, and if the combination of organizations corresponding to the first organization and the second organization exists in the database, the identification unit identifies at least one of the first organization and the second organization as being the same organization as the organization corresponding to the combination registered in the database.

[0010] Furthermore, in the information processing device according to the fourth aspect of the present disclosure, in the third aspect, when there are multiple organizations in the database that have a relationship with the first organization and whose name corresponds to the name of the second organization indicated by the second information, the identification unit identifies the organization among the multiple organizations that has the highest relationship level indicating the degree of relationship with the first organization as being the same organization as the second organization.

[0011] In addition, in the information processing device according to a fifth aspect of the present disclosure, in the fourth aspect, the identification unit sets the relationship degree higher as the number of past interactions with the first organization increases.

[0012] Furthermore, in the information processing device according to the sixth aspect of the present disclosure, in the third aspect, when there are multiple organizations in the database that have a relationship with the first organization and whose name corresponds to the name of the second organization indicated by the second information, the identification unit identifies the largest organization among the multiple organizations as being the same organization as the second organization.

[0013] In addition, in the information processing device according to a seventh aspect of the present disclosure, in the sixth aspect, the identification unit sets the size higher for an organization that has more interactions with other organizations in the database.

[0014] In addition, in the first or second aspect, the information processing device according to the eighth aspect of the present disclosure further includes an identification unit that identifies the second organization based on the region to which the first organization is associated and the registered address of the second organization.

[0015] In addition, the information processing device according to a ninth aspect of the present disclosure, in the first or second aspect, further includes a notification unit that notifies information regarding at least one of the identified first organization and the identified second organization.

[0016] In addition, in the information processing device according to the tenth aspect of the present disclosure, in the ninth aspect, the notification unit notifies at least one of a corporate number and identification information different from the corporate number, in association with at least one of the identified first organization and the identified second organization.

[0017] In addition, in an information processing device according to an eleventh aspect of the present disclosure, in the first aspect, the acquisition unit automatically acquires at least one of the first information regarding the first organization and the second information regarding the second organization from a database.

[0018] In addition, a program according to a twelfth aspect of the present disclosure causes a computer to function as an acquisition unit that acquires first information about a first organization and second information about a second organization different from the first organization, a determination unit that determines whether or not there is a relationship between the first organization and the second organization based on the first information and the second information, and an identification unit that identifies at least one of the first organization and the second organization based on the result of the determination. [Effects of the Invention]

[0019] According to the information processing device and program according to the present disclosure, it is possible to improve the identification accuracy. [Brief explanation of the drawings]

[0020] [Figure 1] 1 is a schematic diagram illustrating an example of an overall configuration of a system according to a first embodiment of the present disclosure. [Figure 2] FIG. 2 is a schematic diagram illustrating an example of a hardware configuration of a server device. [Figure 3] FIG. 2 is a block diagram illustrating an example of various functions of the server device. [Figure 4] FIG. 2 is a diagram illustrating an example of a relational database. [Figure 5] FIG. 10 is a diagram illustrating an example of an organization database. [Figure 6] FIG. 2 is a diagram illustrating an example of a location database. [Figure 7] FIG. 10 is a diagram illustrating an example of a display screen of a user terminal. [Figure 8] FIG. 10 is a diagram illustrating an example of a display screen of a user terminal. [Figure 9] 10 is a flowchart illustrating an example of a processing flow of a server device. [Figure 10] FIG. 10 is a diagram showing an example of a display screen of a user terminal in the system according to the second embodiment of the present disclosure. [Figure 11] 10 shows an example of a database showing counterparty organizations involved in a contract. DETAILED DESCRIPTION OF THE INVENTION

[0021] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. To facilitate understanding of the description, the same components and steps in each drawing will be denoted by the same reference numerals as much as possible, and redundant description will be omitted.

[0022] ===First Embodiment=== First, the first embodiment will be described.

[0023] <Overall structure> FIG. 1 is an overall configuration diagram of a system 1 according to a first embodiment of the present disclosure. The system 1 identifies an organization, for example, in response to a user instruction. Identification involves identifying a target organization. Specifically, identification involves associating the target organization with a pre-registered organization. The target organization is designated by, for example, a user. The organization may be, for example, a company, a school, a government agency, an organization, or the like, but is not limited thereto.

[0024] 1, the system 1 includes a server device 2 and a user terminal 3. The server device 2 and the user terminal 3 are capable of communicating with each other via a network NT.

[0025] The server device 2 is an information processing device (computer) that identifies an organization. The server device 2 may be a cloud-based or on-premise type.

[0026] The user terminal 3 is a terminal device and an information processing device (computer) used by a user. The user terminal 3 is, for example, a personal computer, a smartphone, a tablet, etc. In this embodiment, the user terminal 3 is a personal computer as an example. The user can issue various instructions to the server device 2 using the user terminal 3.

[0027] <Hardware configuration> FIG. 2 is a diagram illustrating an example of a hardware configuration of the server device 2. As shown in FIG.

[0028] 2, the server device 2 includes a control device 10, a communication device 11, a storage device 12, an operation device 13, and a display device 14. The control device 10 is mainly configured to include a CPU (Central Processing Unit) 15 and a memory 16.

[0029] In the control device 10, the CPU 15 executes predetermined programs stored in the memory 16 or the storage device 12, etc., thereby functioning as various functional components described below. The memory 16 is a computer-readable storage medium, and may be composed of at least one of, for example, a random access memory (RAM), a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), etc. The memory 16 can store various types of data, such as programs required to execute processes in the server device 2.

[0030] The communication device 11 is configured with a communication interface and the like for communicating with an external device.

[0031] The storage device 12 is a computer-readable instruction recording medium, and is configured, for example, with a hard disk or a solid state drive. The storage device 12 stores various programs and information required for executing processes in the control device 10, as well as information on the processing results. Note that other examples of non-transitory computer-readable instruction recording media include portable recording media such as magnetic tape, flexible disks, optical disks, digital versatile disks, Blu-ray disks, magneto-optical disks, memory cards, and USB memory.

[0032] The operation device 13 is an input device (for example, a keyboard, a mouse, etc.) that accepts input.

[0033] The display device 14 is a display device (for example, a display) that outputs characters and images.

[0034] The server device 2 can be realized using an information processing device such as a dedicated or general-purpose computer. The server device 2 may be configured with a single information processing device or multiple information processing devices. FIG. 2 shows only a portion of the main hardware configuration of the server device 2, and the server device 2 may have other configurations. The user terminal 3, like the server device 2, is equipped with a control device (CPU and memory), a communication device, a storage device, an operation device, and a display device.

[0035] <Functional configuration> 3 is a block diagram showing an example of various functions in the server device 2. Various processes are executed by the functions in each block.

[0036] As shown in FIG. 3, the server device 2 has, as its functional configuration, the following main components: a memory unit 30, an acquisition unit 31, a determination unit 32, an identification unit 33, a specification unit 34, and a notification unit 35.

[0037] The storage unit 30 stores various databases. Each stored database is referenced by various processes described below. Note that some or all of the databases stored in the storage unit 30 may be stored in a device (e.g., an external device) different from the server device 2 and may be referenced by the server device 2.

[0038] The storage unit 30 includes a relational database DB1, an organization database DB2, and a location database DB3.

[0039] The relational database DB1 is a database in which organizations that are related to each other are associated with each other. A relation indicates that there has been an exchange between organizations. In this embodiment, an example of a relation is the exchange of business cards. In other words, when business cards are exchanged between organizations, a relation exists between the organizations. Note that the relation is not limited to the exchange of business cards, and may be, for example, email, telephone, sales, contract, etc., as long as it can indicate a relationship between organizations.

[0040] In this embodiment, a combination of mutually related organizations registered in the relational database DB1 is referred to as a “registered organization pair.” A registered organization pair indicates the record of exchanges that have taken place between the organizations.

[0041] The relational database DB1 is set in advance to associate related organizations, for example, using input from a user, a business card management database, email history, and the like.

[0042] FIG. 4 shows an example of the relational database DB1. In the relational database DB1, the name and identification information of one organization having a relationship with the name and identification information of the other organization are associated as registered organization pairs. The identification information is information uniquely assigned to each organization, and in this embodiment, it is an identification number. The identification number is, for example, a corporation number. Note that the identification number (identification information) may be an identification number different from the corporation number (e.g., a unique management number). The identification number is a number uniquely assigned to each organization. For example, if there are multiple organizations with the same name, different identification numbers are assigned to each organization. Note that multiple types of identification information (e.g., a corporation number and a management number) may be associated with one organization. In the example of FIG. 4, companies A1 and B1, A2 and B2, and A3 and B3 are associated as registered organization pairs. Note that the contents of each item in FIG. 4 are merely examples. By referring to the relational database DB1 in FIG. 4, it is possible to extract pairs of organizations that have had a relationship in the past. In the relational database DB1, if the relationship between organizations has a directionality, the pair of organizations may be set including the directionality. The directionality may be, for example, the relationship between the organization that provided the business card and the organization that provided the business card, or the sender and recipient of an email. In addition, in the relational database DB1, information such as the content and number of interactions of the relationship may be registered in association with the registered organization pair.

[0043] The organization-specific database DB2 is a database in which attributes are registered corresponding to each of a plurality of organizations. FIG. 5 shows an example of the organization-specific database DB2. In the organization-specific database DB2, the name, address, telephone number, and identification information of an organization are associated with each other. The identification information is, for example, an identification number such as a corporate number, as in the relational database DB1. In the example of FIG. 5, an address, telephone number, and identification number are associated with each of companies C1, C2, and C3. Note that the contents of each item in FIG. 5 are merely examples. A search can be performed for each organization by referring to the organization-specific database DB2 in FIG. 5.

[0044] The location database DB3 is a database in which the location of each of a plurality of organizations is registered. The location is the registered location (head office location). FIG. 6 shows an example of the location database DB3. In the location database DB3, the name of an organization, the location, and identification information are associated with each other. The identification information is, for example, an identification number such as a corporate number, as in the relational database DB1 and the organization-specific database DB2. In the example of FIG. 6, the location and identification number are associated with each of companies E1, E2, and E3. Note that the contents of each item in FIG. 6 are merely examples. A search related to the location can be performed by referring to the location database DB3 in FIG. 6. Note that the location database DB3 may be combined with the organization-specific database DB2.

[0045] As described above, the storage unit 30 has various databases. Note that there may be overlapping items in the relational database DB1, the organization database DB2, and the location database DB3. Furthermore, the databases may be combined, or the databases may be configured in a different way from the above.

[0046] Returning to FIG. 3 , the acquisition unit 31 acquires information about the first organization and information about the second organization. The information about the first organization is referred to as "first information," and the information about the second organization is referred to as "second information." The first organization and the second organization are different organizations. The first information is information indicating the first organization, for example, the name of the first organization. The second information is information indicating the second organization, for example, the name of the second organization. Note that the first information and the second information are not limited to names as long as they are information indicating the respective organizations. For example, one of the first information and the second information may be an identification number indicating the respective organizations. In this embodiment, a case where the first information and the second information are names indicating the respective organizations will be described as an example.

[0047] Specifically, the acquisition unit 31 acquires first information about a first organization and second information about a second organization in response to a user's designation. FIG. 7 is a diagram illustrating an example of a screen 71 displayed on the user terminal 3. An area 72 on the screen 71 is a field where the user inputs the name of the first organization (first information). An area 73 on the screen 71 is a field where the user inputs the name of the second organization (second information). The user inputs a pair of organizations to be identified as the first organization and the second organization. The user completes inputting the names of the first organization and the second organization by pressing a complete button 74 on the screen 71. As the user inputs the first information and the second information in this manner, the acquisition unit 31 acquires the first information and the second information. Note that, as shown in an area 75 on the screen 71, the type of organization may be input (selected) corresponding to each of the first organization and the second organization. Examples of the type of organization include a company and a local government. Note that, as shown in an area 76 on the screen 71, the attributes of the organization may be input (selected) corresponding to each of the first organization and the second organization. Examples of the attributes of the organization include a telephone number and an address. When an input or the like is made in the area 75 or the area 76, the information is included in the first information or the second information together with the information in the area 72 or the area 73 as information relating to the respective organization.

[0048] 3, the determination unit 32 determines whether or not there is a relationship between the first organization and the second organization based on the first information and the second information. Specifically, the determination unit 32 determines that there is a relationship between the first organization and the second organization if there is a history of exchange between the first organization and the second organization. In other words, the determination unit 32 determines whether or not there has been exchange of emails, business cards, or the like between the first organization and the second organization in the past.

[0049] Specifically, the determination unit 32 refers to the relational database DB1 and determines whether a combination of organizations corresponding to the combination of the first organization and the second organization is registered as a registered organization pair in the relational database DB1. Specifically, the determination unit 32 searches the relational database DB1 using the combination of the first information and the second information acquired by the acquisition unit 31. For example, the determination unit 32 searches the relational database DB1 using the name of the first organization and the name of the second organization.

[0050] Then, if a combination of organizations corresponding to the combination of the first organization and the second organization is registered as a registered organization pair, the determination unit 32 determines that there is a relationship between the first organization and the second organization.Furthermore, if a combination of organizations corresponding to the combination of the first organization and the second organization is not registered as a registered organization pair, the determination unit 32 determines that there is no relationship between the first organization and the second organization.

[0051] In this way, the determination unit 32 determines whether or not there is a relationship between the first organization and the second organization specified by the user. In the above example, the determination unit 32 determines whether or not there is a relationship by referring to the relationship database DB1, but the determination may also be made by referring to other information, such as a business card management database or email history.

[0052] The identification unit 33 identifies the first tissue and the second tissue based on the result of the determination by the determination unit 32. Note that the identification unit 33 may identify either the first tissue or the second tissue. The identification unit 33 identifies the first tissue and the second tissue when the determination unit 32 determines that there is a relationship between the first tissue and the second tissue.

[0053] Specifically, when a registered organization pair corresponding to a first organization and a second organization is registered in the relational database DB1, the identification unit 33 identifies the first organization and the second organization as being the same organization as the organization corresponding to the registered organization pair. The first organization is identified as being the same organization as one of the organizations in the registered organization pair whose name matches. The second organization is identified as being the same organization as the other organization in the registered organization pair whose name matches.

[0054] When the identification unit 33 identifies the organizations as being the same, it associates the identification numbers registered in the relational database DB1 with the first organization and the second organization. The first organization is associated with the identification number associated with one of the registered organization pairs with the matching name, and the second organization is associated with the identification number associated with the other of the registered organization pairs with the matching name.

[0055] In this way, the identification unit 33 identifies the first organization and the second organization by associating the acquired first organization and the second organization with the identification number uniquely assigned to the organization, thereby specifying which organization the first organization and the second organization are.

[0056] The identification unit 34 identifies (identifies) the tissue using a method different from that used by the identification unit 33. The identification unit 34 has a first identification unit 37 and a second identification unit 38.

[0057] The first identification unit 37 identifies the first organization in accordance with the attributes of the first organization. The first identification unit 37 also identifies the second organization in accordance with the attributes of the second organization. The attributes include, for example, the name, address, and telephone number of the organization. Specifically, the first identification unit 37 refers to the organization-specific database DB2 to identify each of the first organization and the second organization. The first identification unit 37 searches the organization-specific database DB2 for an organization corresponding to the first organization using the acquired first information. For example, the first identification unit 37 searches the organization-specific database DB2 using the name of the first organization included in the first information, and identifies an organization with the same name as the first organization registered in the organization-specific database DB2. The first identification unit 37 may also perform a search using other information included in the first information (for example, a telephone number or an address). The first identification unit 37 then associates the identification number of the organization registered in the organization-specific database DB2 with the first organization. In this way, the first identification unit 37 identifies the first organization. The first identification unit 37 also searches the organization-specific database DB2 using the name of the second organization included in the second information, and identifies an organization with the same name as the second organization registered in the organization-specific database DB2. The first identification unit 37 may also perform a search using other information included in the second information (for example, a telephone number or an address). The first identification unit 37 then associates the identification number of the organization registered in the organization-specific database DB2 with the second organization. In this way, the first identification unit 37 identifies the second organization.

[0058] In this way, the first identification unit 37 uses the attributes to identify each of the first organization and the second organization.

[0059] The second identification unit 38 identifies the second organization when the first organization is a local government (e.g., a national or local government). For example, when an organization submits a bid to a local government, there may be restrictions on the organization's location. The second identification unit 38 utilizes this characteristic to identify the second organization. Specifically, the second identification unit 38 identifies the second organization based on the region to which the first organization is associated and the registered location of the second organization. Specifically, the second identification unit 38 defines the region to which the first organization is associated as the region governed by the local government. That is, the second identification unit 38 identifies the region of the local government indicated by the first information of the first organization. For example, the second identification unit 38 identifies the region of the local government from the name of the local government indicated by the first information. Furthermore, the second identification unit 38 identifies the registered location of the second organization by referring to the location database DB3. For example, the second identification unit 38 searches the location database DB3 using information such as the name of the second information indicated by the second information, and identifies the registered location (head office location) of the second organization.

[0060] Then, if the registered location of the second organization indicated in the location database DB3 is within the area of ​​the local government, the second identification unit 38 associates the identification number corresponding to the location indicated in the location database DB3 with the second organization.

[0061] In this way, the identification unit 34 identifies the first organization and the second organization by associating the acquired first organization and second organization with the identification number uniquely assigned to the organization. That is, it is possible to identify which organization the first organization and which organization the second organization are.

[0062] That is, the identification unit 33 and the specification unit 34 identify the first organization and the second organization, and associate an identification number with each of them.

[0063] The notification unit 35 notifies the user of information about the identified first organization and second organization. When identification is made for either the first organization or the second organization, information about that organization is notified. The notification unit 35 notifies the user by displaying the identification result on the user terminal 3.

[0064] Specifically, the notification unit 35 notifies the user of the identification numbers associated with the first organization and the second organization. FIG. 8 is a diagram illustrating an example of a screen 81 displayed on the user terminal 3. An area 82 on the screen 81 is a field displaying the identification result of the first organization. That is, the area 82 displays the identification number associated with the first organization. An area 83 on the screen 81 is a field displaying the identification result of the second organization. That is, the area 83 displays the identification number associated with the second organization. Note that the example in FIG. 8 illustrates a case where the identification number of the first organization is "50001" and the identification number of the second organization is "50002." A user viewing the screen 81 can confirm the specific organizations that the input first organization and second organization are based on the identification numbers. For example, even if there are multiple organizations with the same name as the input first organization or second organization, the specific organization can be identified among the organizations with the same name.

[0065] In the above example, one identification number is associated with each of the first organization and the second organization and notified, but multiple identification numbers may be associated with each of the first organization and the second organization, and each of the multiple identification numbers may be notified.

[0066] <Processing flow> 9 is a flowchart showing an example of the flow of the identification process of the server device 2 according to this embodiment. The processes in the following steps are executed when, for example, a start instruction is given by the user. Note that the order and content of the following steps can be changed as appropriate.

[0067] (Step SP10) The acquisition unit 31 acquires first information about the first organization and second information about the second organization. The user inputs a pair of organizations that are assumed to have a relationship, for example, by exchanging business cards, as the first organization and the second organization, and the acquisition unit 31 acquires the input information. Then, the process proceeds to step SP11.

[0068] (Step SP11) The first identification unit 37 uses attributes other than the name to identify the first organization and the second organization in the organization-specific database DB2. Specifically, the first identification unit 37 searches the organization-specific database DB2 using information (other than the name) such as telephone number and address included in the first information, and if a corresponding organization is found, associates the identification number with the first organization. The first identification unit 37 also searches the organization-specific database DB2 using information (other than the name) such as telephone number and address included in the second information, and if a corresponding organization is found, associates the identification number with the second organization. Then, the process proceeds to step SP12.

[0069] (Step SP12) The first identification unit 37 determines whether the first organization and the second organization have been identified using attributes other than the name. If there is no corresponding organization in the organization-specific database DB2, or if there are multiple corresponding organizations in the organization-specific database DB2 and it is not possible to narrow it down to one organization, it is determined that the identification has not been successful. If the first organization and the second organization have been identified, the process proceeds to step SP21. If the first organization and the second organization have not been identified, the process proceeds to step SP13.

[0070] (Step SP13) The determination unit 32 refers to the relational database DB1 and determines whether a combination of organizations corresponding to the combination of the first organization and the second organization is registered as a registered organization pair in the relational database DB1. If the combination of the first organization and the second organization is registered in the relational database DB1, the process proceeds to step SP14. If the combination of the first organization and the second organization is not registered in the relational database DB1, the process proceeds to step SP15.

[0071] (Step SP14) The identification unit 33 associates the identification numbers of each organization registered in the relational database DB1 with the first organization and the second organization. Specifically, the first organization is associated with the identification number associated with one organization in the registered organization pair that has a matching name. The second organization is associated with the identification number associated with the other organization in the registered organization pair that has a matching name. Then, the process proceeds to step SP15.

[0072] (Step SP15) The identification unit 33 determines whether or not the first organization and the second organization have been identified using the relational database DB1. If there is no corresponding registered organization pair in the relational database DB1, or if there are multiple corresponding registered organization pairs in the relational database DB1 and it is not possible to narrow it down to one registered organization pair, it is determined that the identification has not been successful. If the first organization and the second organization have been identified, the process proceeds to step SP21. If the first organization and the second organization have not been identified, the process proceeds to step SP16.

[0073] (Step SP16) If the first organization is a local government, the second identification unit 38 determines whether the registered address of the second organization identified by the location database DB3 is within the area overseen by the local government. If the registered address of the second organization is within the area overseen by the local government, the process proceeds to step SP17. If the registered address of the second organization is not within the area overseen by the local government, the process proceeds to step SP18.

[0074] (Step SP17) The second identification unit 38 associates the identification number corresponding to the location indicated in the location database DB3 with the second organization. Since the first organization is a local government, it is preferable to associate the identification number corresponding to the local government. Then, the process proceeds to step SP18.

[0075] (Step SP18) The second identification unit 38 determines whether the first organization and the second organization have been identified using the location database DB3. It is determined that the identification has failed if there is no corresponding organization in the location database DB3 or if the registered location of the second organization identified by the location database DB3 is not within the area overseen by the local government. It is also determined that the identification has failed if there are multiple organizations corresponding to the second organization in the location database DB3 and each organization is located within the area of ​​the local government, making it impossible to narrow it down to one organization. If the first organization and the second organization have been identified, the process proceeds to step SP21. If the first organization and the second organization have not been identified, the process proceeds to step SP19.

[0076] (Step SP19) The first identification unit 37 uses the names to identify the first organization and the second organization in the organization-specific database DB2. Specifically, the first identification unit 37 searches the organization-specific database DB2 using the name included in the first information, and if a corresponding organization is found, associates the identification number with the first organization. The first identification unit 37 also searches the organization-specific database DB2 using the name included in the second information, and if a corresponding organization is found, associates the identification number with the second organization. Then, the process proceeds to step SP20.

[0077] (Step SP20) The first identification unit 37 determines whether the first organization and the second organization have been identified using the names. If there is no corresponding organization in the organization-specific database DB2, or if there are multiple corresponding organizations in the organization-specific database DB2 and it is not possible to narrow it down to one organization, it is determined that the identification has not been successful. If the first organization and the second organization have been identified, the process proceeds to step SP21. If the first organization and the second organization have not been identified, the process proceeds to step SP22.

[0078] (Step SP21) The notification unit 35 notifies the identification numbers associated with the first organization and the second organization, and the process then ends.

[0079] (Step SP22) The notification unit 35 notifies the user that the first organization and the second organization could not be identified, and the process then ends.

[0080] The identification process is performed as described above. Note that the order of the above processes can be changed. Also, multiple steps may be processed in parallel. Also, in the above example, a case where both the first organization and the second organization are identified is described as an example, but it is also possible to identify only one of them. Also, in the above step, a notification is given in step SP22 that both the first organization and the second organization cannot be identified, but if either the first organization or the second organization can be identified, the identification result of only that one organization may be notified.

[0081] In the above example, if there are multiple organizations that fit the first organization (or the second organization) and it is not possible to narrow it down to one organization, the organization cannot be identified. However, the identification numbers of each of the multiple organizations that fit may be associated with the first organization (or the second organization). Also, the associated identification numbers may be presented to the user, and a selection may be made by the user.

[0082] <Example> Next, a specific example using the above-mentioned identification process will be described.

[0083] (Example EX1) For example, the identification process is used by a user of a company collecting information on bidding projects for local governments. The user recognizes the relationship between the local government and the organization that submitted a bid to the local government, but assumes that there are multiple organizations with the same name as the organization that submitted the bid, making it difficult to identify the bidder. In such a case, the user uses the user terminal 3 to input the local government and the bidder as the first and second organizations, and the above-described identification process identifies the bidder. Specifically, by identifying the bidder's identification number (e.g., corporate number), the user can easily identify the bidder. Furthermore, when the relationships between the organizations are known in advance, as in this example, the above-described identification process enables effective identification, particularly by processing the relational database DB1 by the identification unit 33. Furthermore, when identifying organizations that submitted bids to the local government, the second identification unit 38 can effectively identify the bidder by processing the location database DB3.

[0084] (Example EX2) The identification process is also used by users of companies that have signed contracts with other companies. It is assumed that the user recognizes the name of the company that has signed a contract with the user's company, but there are multiple organizations with the same name as the contracting company, making it difficult to identify the contracting company. In such a case, the user inputs the user's company and the contracting company as the first and second organizations using the user terminal 3, and the contracting company is identified by the above-described identification process. Specifically, by identifying the contracting company's identification number (e.g., corporate number), the user can easily identify the contracting company. Furthermore, when it is known in advance that the two organizations have a relationship (bidding) with each other, as in this example, the above-described identification process enables effective identification, particularly by processing using the relational database DB1 by the identification unit 33.

[0085] For example, by identifying the organization as described above, the user can specify the organization. Furthermore, by identifying the organization, it becomes possible to perform processing such as name identification.

[0086] <Action and effect> As described above, the server device 2 according to this embodiment includes an acquisition unit 31 that acquires first information about a first organization and second information about a second organization different from the first organization, a determination unit 32 that determines whether or not there is a relationship between the first organization and the second organization based on the first information and the second information, and an identification unit 33 that identifies at least one of the first organization and the second organization based on the result of the determination.

[0087] According to this configuration, since the relationship between the first organization and the second organization is used for identification, it is possible to improve the accuracy of identification. For example, even if there are multiple organizations with the same name and it is difficult to perform identification efficiently, it is possible to effectively narrow down the target and perform identification by using the relationship between the organizations.

[0088] Furthermore, in the server device 2, the determination unit 32 determines that there is a relationship between the first organization and the second organization when there is a history of exchange between the first organization and the second organization.

[0089] According to this configuration, when there is a history of exchange between organizations, the targets are narrowed down due to the relationship between the organizations, so that efficient identification becomes possible.

[0090] Furthermore, in the server device 2, the determination unit 32 refers to a relational database DB1 in which combinations of mutually related organizations are registered, and determines whether or not there is a combination of organizations corresponding to a first organization and a second organization in the relational database DB1, and if there is a combination of organizations corresponding to the first organization and the second organization in the relational database DB1, the identification unit 33 identifies at least one of the first organization and the second organization as being the same organization as the organization corresponding to the combination registered in the relational database DB1.

[0091] According to this configuration, the combination of the first organization and the second organization can be collated with the relational database DB1 to identify the first organization and the second organization.

[0092] The server device 2 further includes an identification unit 34 that identifies the second organization based on the region to which the first organization is associated and the registered address of the second organization.

[0093] According to this configuration, when there is a relationship between a first organization and a second organization, such as a bidding relationship, it becomes possible to identify the first organization and the second organization based on their registered address.

[0094] The server device 2 further includes a notification unit 35 that notifies information about at least one of the identified first organization and second organization.

[0095] According to this configuration, for example, the user can identify the first organization and the second organization by checking the notified information.

[0096] Furthermore, in the server device 2, the notification unit 35 notifies at least one of the corporation number and identification information different from the corporation number, in association with at least one of the identified first organization and second organization.

[0097] According to this configuration, by being notified of an identification number such as a corporation number, the user can easily identify the organization, for example.

[0098] === Second Embodiment === Next, a second embodiment will be described.

[0099] In the second embodiment, a process will be described for a case where multiple organizations that have a relationship with a first organization and have the same name as a second organization are registered in the relational database DB1. Note that a description of the same points as in the first embodiment will be omitted. Also, the second embodiment can be combined with the first embodiment.

[0100] In this embodiment, when there are multiple organizations in the relationship database DB1 that have a relationship with the first organization and whose names correspond to the name of the second organization indicated by the second information, the identification unit 33 identifies the second organization based on the relationship degree. A name that corresponds to the name of the second organization includes cases where the names are the same or similar. The relationship degree is an index indicating the degree of relationship with the first organization, and is set to a higher value the more times an organization has previously exchanged business cards with the first organization. For example, the relationship degree is set to a higher value the more times an organization has exchanged business cards with the first organization.

[0101] The identification unit 33 identifies the organization with the highest degree of relationship among multiple relevant organizations in the relational database DB1 as the same organization as the second organization. For example, if there are five organizations in the relational database DB1 that have a relationship with the first organization and whose name corresponds to the name of the second organization, the identification unit 33 identifies the organization with the highest degree of relationship with the first organization among the five organizations as the same organization as the second organization. Then, the identification unit 33 associates the identification number associated with the organization with the highest degree of relationship with the first organization in the relational database DB1 with the second organization. In this way, the second organization is identified.

[0102] The identification result of the second organization is then notified by the notification unit 35. FIG. 10 is a diagram showing an example of a screen 101 displayed on the user terminal 3. The identification result of the first organization is displayed in area 102. Area 103 of the screen 101 is a column for displaying the identification result of the second organization. That is, area 103 displays the identification number associated with the second organization. Note that the example of FIG. 10 shows an example in which the identification number of the first organization is "60001" and the identification number of the second organization is "60002." Furthermore, when there are multiple candidates corresponding to the second organization, as in this embodiment, the identification numbers of the other candidates may be displayed as shown in area 104. For example, when there are five organizations that have a relationship with the first organization and have the same name as the second organization, the identification number corresponding to the organization with the highest relationship level among the five organizations is displayed in area 103. Furthermore, the identification numbers of the other four organizations (organizations other than the organization with the highest relationship level) are displayed in area 104. 10 shows an example in which other candidates for the identification number of the second organization are "60003," "60004," "60005," and "60006." When displaying other candidates, they may be displayed in descending order of the degree of relationship.

[0103] Furthermore, when there are multiple organizations in the relational database DB1 that have a relationship with the first organization and whose name corresponds to the name of the second organization indicated by the second information, the identification unit 33 may identify the second organization based on the size of the organization. The size of an organization is set to a higher value the more frequently an organization interacts with other organizations in the relational database DB1. For example, the size is set to a larger value the more frequently business cards are exchanged with other organizations (not limited to the first organization). In other words, the size is set on the assumption that the more frequently an organization interacts with other organizations, the larger the organization.

[0104] The identification unit 33 identifies the largest organization among the multiple relevant organizations in the relational database DB1 as the same organization as the second organization. For example, if the relational database DB1 has five organizations that have a relationship with the first organization and whose name corresponds to the name of the second organization, the identification unit 33 identifies the largest organization among the five organizations as the same organization as the second organization. Then, the identification unit 33 associates the identification number associated with that organization in the relational database DB1 with the second organization. In this way, the second organization is identified.

[0105] When the second organization is identified using the size of the organization, notification is made, for example, as in Fig. 10. Note that, similar to Fig. 10, other candidates for the second organization (organizations other than the largest organization) may be displayed. When displaying other candidates, they may be displayed in descending order of size.

[0106] <Action and effect> In the server device 2 according to this embodiment, when there are multiple organizations in the relational database DB1 that have a relationship with the first organization and whose name corresponds to the name of the second organization indicated by the second information, the identification unit 33 identifies the organization with the highest relationship level indicating the degree of relationship with the first organization among the multiple organizations as being the same organization as the second organization.

[0107] With this configuration, even if multiple organizations are applicable, it is possible to identify and classify the organization with the highest probability. By using the degree of relationship between the first organization and the second organization, it is possible to effectively identify the organization with the highest probability.

[0108] Furthermore, in the server device 2, the identification unit 33 sets a higher relationship degree as the number of past interactions with the first organization increases.

[0109] According to this configuration, the degree of relationship can be appropriately evaluated based on the number of interactions that have taken place in the past.

[0110] Furthermore, in the server device 2, when there are multiple organizations in the relational database DB1 that have a relationship with the first organization and whose name corresponds to the name of the second organization indicated by the second information, the identification unit 33 identifies the organization that is largest among the multiple organizations as being the same organization as the second organization.

[0111] With this configuration, even if multiple organizations are applicable, it is possible to identify and classify the organization with the highest probability. By using the size of the organization, it is possible to effectively identify the organization with the highest probability.

[0112] Furthermore, in the server device 2, the identification unit 33 sets a higher scale for an organization that has more interactions with other organizations in the relational database DB1.

[0113] According to this configuration, the scale can be appropriately evaluated based on the number of exchanges (without limiting the organization) registered in the relational database DB1.

[0114] <Modification> The present disclosure is not limited to the above-described embodiments. In other words, variations of the above-described embodiments, which are appropriately modified by a person skilled in the art, are also included within the scope of the present disclosure as long as they include the features of the present disclosure. Furthermore, the elements of the above-described embodiments and the modifications described below can be combined to the extent technically possible, and such combinations are also included within the scope of the present disclosure as long as they include the features of the present disclosure.

[0115] For example, in the first embodiment, the server device 2 has each function, but each function may be provided in the user terminal 3. Furthermore, each function may be distributed between the server device 2 and the user terminal 3.

[0116] Furthermore, in the first embodiment, a case where a user inputs first information about a first organization and second information about a second organization and the acquisition unit 31 acquires the input information is described as an example. However, this is not limited to the above. For example, the acquisition unit 31 may acquire the first information about the first organization and the second information about the second organization automatically set by a calculation process or the like. For example, if the names of multiple organizations (counterparties) that have concluded contracts with G1 are registered in the database of G1 company, an identification process may be automatically performed using the database. FIG. 11 shows an example of a database that lists multiple counterparties that have concluded contracts with G1 company. For example, as shown in area 111, the contract IDs are associated with the names of the counterparties. In this case, the acquisition unit 31 acquires G1 company (name and identification information) as the first organization and the name of the counterparty organization (e.g., H1 company) as the second organization. Then, by performing the identification process, the identification information (e.g., corporate number) of each counterparty organization is specified and identified, as shown in area 112 of FIG. 11. The example in FIG. 11 illustrates a case in which H1 Company and H2 Company are essentially the same organization, despite minor differences in their names (e.g., whether or not they are incorporated), and are assigned the same corporate number. Thus, the first organization and the second organization do not necessarily have to be specified by a user, but may be automatically acquired by referencing a database or the like. For example, there may be a case in which K1 Company provides a service (e.g., SaaS) and K2 Company uses the service, and the names of multiple companies (e.g., K3 Company, etc.) entered on the SaaS are registered in a database. In such a case, the acquisition unit 31 may acquire a pair of K2 Company and the multiple registered companies (e.g., K3 Company, etc.) as the first organization and the second organization, and perform the identification process. Particularly when only the names of the organizations are registered in the database (no identification information), automatic organization identification is possible. In this way, the acquisition unit 31 may automatically acquire both (or at least one of) first information (e.g., name) related to the first organization and second information (e.g., name) related to the second organization from the database. This database may be a database that the server device 2 has, or a database that a device other than the server device 2 has.The identification process is performed using the automatically acquired first information and second information. By performing the process using information from a database registered in advance, each organization in the database can be identified.

[0117] In the first embodiment, the name and identification information of one organization that has a relationship with the name and identification information of the other organization are associated as a registered organization pair in the relational database DB1, but this is not limited to the above. For example, other information such as an address or telephone number may be registered in association with each organization. In this case, the acquisition unit 31 can acquire first information and second information in association with each piece of information registered in the relational database DB1.

[0118] Furthermore, in the first embodiment, the first information and the second information are each a name, but the first information and the second information are not limited to being the same type of information. That is, the first information and the second information may be different types of information. For example, the first information may be a corporate number indicating the first organization, and the second information may be a name indicating the second organization. In this case, the identification unit 33 performs identification to associate the identification number with the second organization that has not been identified (the identification number has not been specified).

[0119] 7 shows an example of a screen related to the acquisition of the first information and the second information, but it may be possible to specify whether or not identification is required for the first organization and the second organization. If the necessity of identification is specified, the identification process is performed on organizations that particularly require identification.

[0120] Furthermore, in the second embodiment, a case has been exemplified in which the relationship level is set to a higher value as the number of past interactions increases, but this is not limited to the above. For example, the relationship level may be set according to the content of the interaction. For example, the relationship level is set according to the type of past interaction. The type of interaction may be, for example, email, phone call, business card exchange, contract conclusion, etc., and when an interaction that is considered to be a close relationship (for example, a contract) has taken place, the relationship level is set higher than when an interaction that is considered to be a less close relationship (for example, email) has taken place.

[0121] In the second embodiment, the size of an organization is set to a higher value for an organization that has more interactions with other organizations in the relational database DB1, but this is not limitative. For example, the size of an organization may be set based on the number of employees, sales, etc. of the organization.

[0122] In the first and second embodiments, the acquiring unit 31 acquires two organizations, a first organization and a second organization, but may acquire a combination of three or more organizations. Furthermore, the relational database DB1 may register a combination of three or more mutually related organizations.

[0123] Furthermore, in the first and second embodiments, when searching a database such as the relational database DB1 using a name, for example, a case where an object with a matching name is searched is taken as an example, but this is not limited to a case where the name matches. For example, objects with similar names or objects whose names are presumed to be the same may be searched. Furthermore, a search may be performed after processing the name, etc. For example, a process may be performed to delete unnecessary parts of the name of an organization. For example, if the name includes a company name and a department name, the company name portion may be extracted. Note that the above description uses a name as an example, but the same applies to other parts such as addresses. [Explanation of symbols]

[0124] 2: Server device (information processing device) 31: Acquisition part 32: Judgment section 33: Identification unit

Claims

1. an acquisition unit that acquires first information about a first organization and second information about a second organization different from the first organization; a determination unit that determines whether or not there is a relationship between the first organization and the second organization based on the first information and the second information; an identification unit that identifies at least one of the first texture and the second texture based on a result of the determination; An information processing device comprising:

2. The determination unit determines that a relationship exists between the first organization and the second organization when there is a history of exchange between the first organization and the second organization. The information processing device according to claim 1 .

3. the determination unit refers to a database in which combinations of organizations that are related to each other are registered, and determines whether or not the combination of organizations corresponding to the first organization and the second organization exists in the database; when the combination of organizations corresponding to the first organization and the second organization is present in the database, the identification unit identifies at least one of the first organization and the second organization as the same organization as the organization corresponding to the combination registered in the database; 3. The information processing device according to claim 1 or 2.

4. When there are multiple organizations in the database that have a relationship with the first organization and whose name corresponds to the name of the second organization indicated by the second information, the identification unit identifies the organization that has the highest relationship level indicating the degree of relationship with the first organization among the multiple organizations as the same organization as the second organization. The information processing device according to claim 3 .

5. The identification unit sets the relationship degree higher as the number of past interactions with the first organization increases. The information processing device according to claim 4 .

6. When there are multiple organizations in the database that have a relationship with the first organization and whose name corresponds to the name of the second organization indicated by the second information, the identification unit identifies the largest organization among the multiple organizations as the same organization as the second organization. The information processing device according to claim 3 .

7. The identification unit sets the size to be higher for an organization that has a greater number of interactions with other organizations in the database. The information processing device according to claim 6 .

8. an identification unit that identifies the second organization based on the region to which the first organization is associated and the registered address of the second organization; The information processing device according to claim 1 or 2, further comprising:

9. a notification unit that notifies information about at least one of the identified first organization and the identified second organization; The information processing device according to claim 1 or 2, further comprising:

10. The notification unit notifies at least one of a corporate number and identification information different from the corporate number in association with at least one of the identified first organization and the identified second organization. The information processing device according to claim 9 .

11. the acquiring unit automatically acquires at least one of the first information regarding the first organization and the second information regarding the second organization from a database; The information processing device according to claim 1 .

12. Computer, an acquisition unit that acquires first information about a first organization and second information about a second organization different from the first organization; a determination unit that determines whether or not there is a relationship between the first organization and the second organization based on the first information and the second information; an identification unit that identifies at least one of the first texture and the second texture based on the result of the determination; A program that functions as a

Images