System and method for probabilistic matching of multiple event logs to single real-world ad serve event

Abstract

A system and method for accurately matching corresponding DSP event data and Ad-Server event data with associated with a single real-world ad serve event by (a) pairing DSP event data and Ad-Server event data into data pairs, (b) comparing various field data in associated source fields from each of the DSP event data and Ad-Server event data to determine if the field data is a match or unmatch, and (c) based on the likelihood that a match of field data in a particular source field indicates an overall event match, which is determined using a Bayesian analysis, determining the probability that the DSP event data and Ad-Server event data in the data pair truly corresponding to the same single real-world ad serve event.

Claims

1. A computer-implemented method for accurately matching corresponding demand-side platform DSP event data and Ad-Server event data associated with a single real-world ad serve event, the method comprising the steps of: a. at a common server, receiving from the DSP a set of DSP event data from a DSP source set, each piece of DSP event data comprising a series of DSP source fields having a field data value and wherein at least two of the DSP event data are DSP geographic event data; b. at the common server, receiving from an ad server a set of Ad-Server event data from an Ad-Server source set, each piece of Ad-Server event data comprising a series of Ad-Server source fields having a field data value and wherein at least two of the Ad-Server event data are Ad-Server geographic event data; c. combining each piece of DSP geographic event data into a combined DSP comparison field, combining each piece of Ad-Server event data into a combined Ad-Server comparison field, and pairing each piece of DSP event data with each piece of Ad-Server event data to create a data matrix stored at the common server, wherein the data matrix comprises a plurality of DSP-Ad Server event data pairs; d. for each of the plurality of DSP-Ad Server event data pairs in the data matrix: i. comparing the data value of each DSP source field with the data value of each corresponding Ad-Server source field to create a set of pair fields; ii. assigning a Pair Attribute to each pair field in the set of pair fields, wherein the Pair Attribute for each pair field comprises a first value attribute and a second value attribute, wherein the first value attribute comprises a Boolean attribute indicating one of (a) a field data match of the pair filed and (b) a field data unmatch of the pair field, and wherein the second value attribute comprises one of (a) the data vale of the pair field if the field data is a match and (b) a null value if the field data is an un-match; and iii. using the assigned Pair Attributes in the set of pair fields to determine the probability that the DSP event data and the Ad-Server event data of the particular DSP-Ad Server event data pair are both associated with a single real-world ad serve event using a Bayesian analysis according to $\frac{P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)}{P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)+\underset{j\ne i}{.Math.}(P{1}_j\times \underset{k\ne j}{.Math.}〚\left(1-P{1}_k\right))〛}=P{1}_i\times \frac{\underset{j\ne i}{.Math.}\left(1-P{1}_j\right)}{P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)+\underset{j\ne i}{.Math.}(P{1}_j\times \underset{k\ne j}{.Math.}〚\left(1-P{1}_k\right))〛}=P{1}_i^{*}$ where P1.sub.i is the probability value of each pair field, j ≠ i denotes all pairs in a same pair cohort as pair i other than pair i, and k ≠ j denotes all pairs in the same pair cohort as pair i other than pair j and including pair i; e. determining a decision threshold by a clustering classification model; and f. applying the decision threshold to the probability for each pair field in the set of pair fields to determine whether a pair field represents a match.

2. The method of claim 1, wherein the DSP source fields comprise at least one of (a) a timestamp, (b) location information, (c) operating system information, and (d) website information.

3. The method of claim 2, wherein the Ad-Server source fields comprise at least one of (a) a timestamp, (b) location information, (c) operating system information, and (d) website information.

4. The method of claim 1, further comprising the step of prior to creating the event data pairs applying a filter to reduce the number of event data pairs to be created.

5. The method of claim 4 wherein applying the filter comprises the steps of: a. segregating the DSP event data into a plurality of unit groups; b. segregating the Ad-Server event data into the unit groups; c. defining a time-difference window; and d. for each of the unit groups, pairing the DSP event data in the unit group and the Ad-Server event data in the unit group and filtering out all pairs that fall outside of the time-difference window.

6. The method of claim 1, wherein the Boolean value of the Pair Attribute indicating a field data match is 1 and the Boolean value of a Pair Attribute indicating a field data unmatch is 0.

7. A system for matching data associated with an ad serve event, the method comprising the steps of: a demand-side platform (DSP) comprising one or more computer readable storage devices configured to store a plurality of DSP executable instructions and further comprising one or more DSP hardware computer processors in communication with the one or more DSP computer readable storage devices and configured to execute the plurality of DSP computer executable instructions in order to cause the demand-side platform to generate a set of DSP event data, each piece of DSP event data comprising a series of DSP source fields having a DSP field data value, wherein at least two of the DSP event data are DSP geographic event data; an ad server comprising one or more ad server computer readable storage devices configured to store a plurality of ad server executable instructions and further comprising one or more ad server hardware computer processors in communication with the one or more ad server computer readable storage devices and configured to execute the plurality of ad server computer executable instructions in order to cause the ad server to generate a set of ad server event data, each piece of ad server event data comprising a series of ad server source fields having an ad server field data value, wherein at least two of the ad server event data are ad server geographic event data; a common server comprising one or more common server computer readable storage devices configured to store a plurality of common server executable instructions and further comprising one or more common server hardware computer processors in communication with the one or more common server computer readable storage devices and configured to execute the plurality of common server computer executable instructions in order to cause the common server to receive from the DSP the set of DSP event data and to receive from the ad server the set of ad server event data, combine each piece of DSP geographic event data into a combined DSP comparison field, combine each piece of ad server event data into a combined ad server comparison field, pair each piece of DSP event data with each piece of ad server event data to create a data matrix wherein the data matrix comprises a plurality of DSP to ad server event data pairs, store the data matrix at the common server computer readable storage devices, and, for each of the plurality of DSP-Ad Server event data pairs in the data matrix, compare the data value of each DSP source field with the data value of each corresponding ad server source field to create a set of pair fields, assign a pair attribute to each pair field in the set of pair fields, wherein the pair attribute for each pair field comprises a first value attribute and a second value attribute, wherein the first value attribute comprises a Boolean attribute indicating one of (a) a field data match of the pair filed and (b) a field data unmatch of the pair field, and wherein the second value attribute comprises one of (a) the data vale of the pair field if the field data is a match and (b) a null value if the field data is an un-match, use the assigned Pair Attributes in the set of pair fields to determine the probability that the DSP event data and the ad server event data of the particular DSP to ad server event data pair are both associated with a single real-world ad serve event using a Bayesian analysis according to $\frac{P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)}{P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)+\underset{j\ne i}{.Math.}(P{1}_j\times \underset{k\ne j}{.Math.}〚\left(1-P{1}_k\right))〛}=P{1}_i\times \frac{\underset{j\ne i}{.Math.}\left(1-P{1}_j\right)}{P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)+\underset{j\ne i}{.Math.}(P{1}_j\times \underset{k\ne j}{.Math.}〚\left(1-P{1}_k\right))〛}=P{1}_i^{*}$ where P1.sub.i, is the probability value of each pair field, j ≠ i denotes all pairs in a same pair cohort as pair i other than pair i, and k ≠ j denotes all pairs in the same pair cohort as pair i other than pair j and including pair i, determine a decision threshold by a clustering classification model, and apply the decision threshold to the probability for each pair field in the set of pair fields to determine whether a pair field represents a match.

8. The system of claim 7, wherein the DSP source fields comprise at least one of (a) a timestamp, (b) location information, (c) operating system information, and (d) website information.

9. The system of claim 8, wherein the ad server source fields comprise at least one of (a) a timestamp, (b) location information, (c) operating system information, and (d) website information.

10. The system of claim 7, wherein the one or more common server hardware computer processors are further configured to execute the plurality of common server computer executable instructions in order to create the event data pairs by applying a filter to reduce the number of event data pairs to be created.

11. The system of claim 10, wherein applying the filter comprises segregating the DSP event data into a plurality of unit groups, segregating the ad server event data into the unit groups, defining a time-difference window, and, for each of the unit groups, pairing the DSP event data in the unit group and the ad server event data in the unit group and filtering out all pairs that fall outside of the time-difference window.

12. The system of claim 7, wherein the Boolean value of the pair attribute indicating a field data match is 1 and the Boolean value of a pair attribute indicating a field data unmatch is 0.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a diagram representing DSP Event and Ad-Server event pairs, showing example source fields (state, city, operating system, etc.) for each event of the event pair.

(2) FIG. 2 is a diagram representing the comparison of the field data in each of the example source fields for a paired DSP Event and Ad-Server Event, indicating whether the field data in each source field is a match and assigning a two-value Pair Attribute based on whether the field data is matches.

(3) FIG. 3 is a table showing a number of event data sets and associated source fields, which are assigned two-value Pair Attributes based on the field data match or field data unmatch of the data in the associated source field and wherein the two-value Pair Attributes are organized into a data matrix.

(4) FIG. 4 is a diagram showing the system of the present invention including the consumer, the DSP and its event log data, the Ad Server and its event log data, and the combination of DSP event data and Ad Server event data into a DSP-Ad Server Pair.

(5) FIG. 5 is a modification to FIG. 4 showing the inclusion of a Common Server.

DETAILED DESCRIPTION OF THE INVENTION

(6) Generally speaking, the present invention in certain implementations is directed to a system and method for matching corresponding DSP log events 4 and Ad Server log events 6 associated with a single real-world impression, as shown in the figures. The invention utilizes a series of steps to create and quantify two novel factors (independent geographic closeness factor and the sole rightful heir factor) from the event log data 4, 6 and applies a probability analysis to those factors to determine whether a particular DSP log-Ad server pair 2a is a Match (meaning that both the DSP log event 4 and Ad Server log event 6 of the particular pair 2a do, in fact, correspond to the same real-world impression) or an Unmatch (meaning that the pair 2a does not correspond to the same real-world impression). Generally speaking, the invention in certain implementations includes the following broad steps: (a) log events from both data sources are segregated into smaller unit groups corresponding to individual advertisers and to discrete, identifiable units within each advertiser's overall strategy, (b) a time-difference window W.sub.T is defined, within which most Match pairs are expected to fall, (c) DSP-Ad Sever candidate Pairs 2 (which may be referred to herein simply as “Pairs”) that fall within the time-difference window W.sub.T are created for each group, (d) data fields 7 of the Pairs 2 are compared to create a row of two-valued Pair Attributes for each Pair 2, (e) for each row of two-valued Pair Attributes, the probability that the two events correspond to the same impression is determined, and (f) the pairwise match probabilities produced in step (e) are compared for every potential matching pair and the sole-rightful-heir factor sorts candidate pairs into Match and Unmatch. One or more of these steps may be modified, eliminated, or substituted depending on the user's desired use, and it is understood that one or more of these steps may have a series of sub-steps that achieve the goal of the particular step, as described more fully below. In any event, this general method is utilized by the invention in certain implementations to determine whether a Pair is a Match or an Unmatch.

(7) As noted above, the preferred first step in determining whether a particular Pair 2a is a Match or an Unmatch (and thus whether the Pair 2a does or does not correspond to the same real-world impression) is reducing the search space by segregating events into unit groups and then applying a filter that keeps only those pairs that fall within the time-difference window W.sub.T for further analysis. These two steps enable creating the candidate Pairs 2 to be analyzed. In this regard, the invention uses a mix of deterministic and probabilistic record matching, starting with events recorded over a short time period (preferably twenty-four hours) in both the Ad Server and DSP logs. This filtering function reduces the field of pairs into a more manageable field of candidate pairs by segregating all events from the Ad Server's log during a selected time period (for example, twenty-four hours) and all events from the DSP's log during the same time period into “unit groups” corresponding to individual advertisers and to discrete units within each advertiser's larger strategy using certain identifying values in the log data. A time-difference window W.sub.T is defined, the time-difference window identifying a window of time in which most Match pairs are expected to fall. A comparison of every event from the Ad Server's log in a given unit group with every event from the DSP's log in the same unit group is performed and all pairs that do not fall within the time-difference window W.sub.T are filtered out (as they are most unlikely to be Match pairs). This creates a series of candidate Paris, and the field values of the other source fields are compared for all of the candidate Pairs. At this stage, the Pairs 2 are either a Match or an Unmatch, but such classification is not known until the remaining portion of the implementation is utilized to make that determination. A diagram showing examples of these Pairs 2 is shown in FIG. 1.

(8) As noted previously, the DSP event logs 4 and Ad-Server event logs 6 to be paired 4 and compared for matching are generated by a demand service provider (DSP) 7 and Ad Server 9, respectively, as shown in FIG. 4. These event logs 4, 6 contain data associated with ad-serve events, or the digital display of advertisements to users 3 on user devices 5 (otherwise known as “impressions”). In this regard, the system and method of the present invention can be utilized within existing ad-serve technological environments (such as those that use real time bidding technology such as DSPs and SSPs over an ad network) to improve the tracking and identification of digital consumer activity without violating the privacy of any such consumers. To create the event log data sets 4, 6 for which the present invention is utilized, digital users 3 access the internet from user devices 5 (which may, for example, incorporate a browser or other content-viewing application), and when a user 3 views an eligible display space on the user device 5, the DSP 7 processes bids for the ad display on behalf of advertisers and the Ad Server 9 then delivers the ad to the user's device 5. Each of these generates log data 4, 6 for the event, and, of course, this happens for multiple ad events associated with multiple different users 3. These event logs 4, 6 may be stored in a database and may, in one embodiment, be stored or transferred to a common server 11 (as shown, for example, in FIG. 5), where the record matching of the present invention is utilized to compare the event logs 4, 6 to determine which of the pairs 2 are truly Matches.

(9) Each event 4, 6 from each source set has associated with it a series of data values that are associated with specific data fields 8. For example, both data sets report geographic location (state, city, zip code, etc.), time, the website where the ad was delivered, and a number of other data values for each impression event 4, 6. The two data sets 4, 6 contain many differing such fields, but the preferred implementation focuses on comparing those that appear to be “like for like,” which may include, for example, the following: (a) the timestamp of the impression event, (b) the state in which the user was physically located for the impression event, (c) the metro area in which the user was physically located for the impression event, (d) the city in which the user was physically located for the impression event, (e) the 5-digit zip code in which the user was physically located for the impression event, (f) the operating system being used by the user, (g) the browser being used by the user, and (g) the site on which the ad was delivered, as shown, for example, in FIGS. 1-2. Each of these fields may be referred to as a “source field,” and comparing the source fields 8 (as shown for example, in FIG. 2) for each Pair 2 creates a row of “pair fields” corresponding to each such Pair 2. Most of the pair fields will be two-valued and will include (i) a simple Boolean variable indicating whether the individual source fields are direct matches (as described more fully below and as shown, for example, in the diagram of FIG. 2 and the table in FIG. 3), and (ii) the value on which the source fields match, if they do indeed match.

(10) For all pairs in a given unit group that fall within the time-difference window W.sub.T, the source fields 8 (for example, those listed above, or other similar fields) of each of the two individual events in each Pair 2 are compared to create Pair Attributes for each such Pair 2. The Pair Attributes may include both a Boolean value indicating whether the values in each of the corresponding source fields 8 is the same or different, as shown for example in FIG. 2. One value (such as a “1”, for example) for the Boolean value of the Pair Attribute indicates that the values in the corresponding source fields 8 of a Pair 2 match, while a second value (such as a “0” for example) would indicate that the values in the corresponding source fields 8 do not match. In the case of a source field match, the second part of the Pair Attribute indicates the value on which the two source fields match. In the case of the source field not matching, the second part of the Pair Attribute is simply “null.”

(11) A data matrix is thus formed with one axis (such as the rows) corresponding to a single candidate Pair 2 and the other axis (for example the columns) providing the Pair Attributes, which as noted above, may include (a) Boolean values representing whether the values in the given source fields 8 in the individual logs match (as indicated by a “1”) or do not match (as indicated by a “0”) and (b) the value on which any such source field match occurs. An example of such a matrix is provided in FIG. 3. It should be noted, of course, that this matching of values in the source fields 8 (i.e., two events happened in the same city or on the same type of device) is not the same as the ultimate determination whether the Pairs 2 themselves are a Match or an Unmatch (i.e. correspond to the same ad-serve event or not). While the match/unmatch nature of the source field 8 values are preferably denoted by Boolean values 1 and 0, the Match/Unmatch classification of Pairs 2 themselves may be denoted by different values, such as M (for Match) and U (for Unmatch) for purposes of describing the invention with clarity. In the case where the concept of the real-world match (or not-match) of the information represented by a single field for a given pair must be considered separately from the field values reported by the two event logs either matching or not (a 1 or a 0), lower case “match” and “unmatch,” or “m” and “u” may be utilized for clarity.

(12) As shown in FIG. 3, the matrix may include a number of columns corresponding to the number of source fields 8 compared for each of the events in a source set. As shown in column four, for example, the values “1” or “0” indicate whether the state in which the user was physically located for the impression event was the same or different for each of the Pairs 2. As shown, the first Pair (which corresponds with the values shown in row 1) has a “State Match column” value of 0, indicating that the Ad-Server event and DSP event reported different states (an example is shown in FIG. 2, where the top pair the DSP event data shows the state of California and the Ad Server event data shows the state of New York—no match). For purposes of the preferred embodiment, the values in the various source fields are said to match (“1”) if the following are found to be true: (b) the states reported by the Ad Server event and the DSP event are the same, (c) the metro reported by the Ad Server event and the DSP event are the same, (d) the city reported by the Ad Server event and the DSP event are the same, (e) the zip codes, and separately the first 4, 3, and 2 digits of the zip codes, reported by the Ad Server event and the DSP event are the same, (f) the operating systems reported by the Ad Server event and the DSP event are the same, (g) the browsers reported by the Ad Server event and the DSP event are the same, and (h) the sites reported by the Ad Server event and the DSP event are the same. From each such row of Pair attributes, the probability that two events forming the Pair correspond to the same real-world event of a user being delivered an impression (i.e. whether the Pair 2 is a Match or Unmatch) can be determined.

(13) The Bayesian analysis of the present invention utilizes the principles of Bayes' Theorem, which provides the following:

(14) $P\left(H.Math.E\right)=\frac{P\left(E.Math.H\right)\times P\left(H\right)}{P\left(E\right)},\mathrm{for}H=\mathrm{hypothesis}\mathrm{and}E=\mathrm{evidence}$
For the present invention, the hypothesis for each Pair is the state “Match,” represented with a capital “M” (and where necessary “Unmatch” is represented with a capital “U”). The evidence (E) that is used to inform about the truth or falsity of the hypothesis (that a selected Pair is a Match) consists of the row of Pair Attribute values corresponding to that Pair, as portrayed in the example table shown in FIG. 3. For each Pair the question is “what is the probability that the two log events in this pair represent the same real-world event, given the values that make up the pair attributes associated with this pair?,” or, put in terms of Bayes' Theorem, “what is P(H|E)?” For each Pair, then, the above equation is considered in the following terms:

(15) $\begin{array}{cc}P\left(M.Math.E\right)=1-P\left(U.Math.E\right)=1-\frac{P\left(E.Math.U\right)\times P\left(U\right)}{P\left(E\right)}\mathrm{for}M=\mathrm{Match}\mathrm{and}\text{.Math.}\mathrm{for}E=\mathrm{set}\mathrm{of}\mathrm{Comparison}\mathrm{field}\mathrm{values}\left\{e_i\right\}& \left(\mathrm{Equation}1\right)\end{array}$
This equation may be referred to as Equation 1. Every Pair is either a Match or an Unmatch, from which we know that P(M|E)=1−P(U|E). The three terms appearing on the right side of Equation 1 are discussed more fully below.

(16) First the term P(E|U) can be discussed in detail. While the present invention does consider whether the Pairs are a Match given the entire row of values (E={e.sub.1, e.sub.2, . . . , e.sub.n}) for all Comparison Fields, the Comparison Fields must first be analyzed individually (the individual e.sub.i values). Assuming that the e.sub.i are independent of one another, then this relationship can be expressed by the probability corresponding to the entire row P(M|E) equaling the product of the individual probabilities P(M|e.sub.i) for each Comparison Field value in that row:
P(E|U)=Π.sub.i=1.sup.e.sup.i.sup.∈EP(e.sub.i|U)  (Equation 2)
assuming the e.sub.i are all pairwise independent. There is one large exception to this independence condition: because the four geographic Comparison Fields (State, Metro, City, Zip) are not independent of one another, they must be combined into a single aggregate Comparison Field that both (a) is independent of the other e.sub.i in Equation 2, and (b) preserves the information contained in the four geographic e.sub.i. This single aggregate geographic Comparison Field (which is referred to as e.sub.G) is then included among the e.sub.i in place of the four previous geographic fields, and along with the non-geographic Comparison Fields, in the product of Equation 2:
P(E|U)=P(e.sub.G|U)×Π.sub.i=1.sup.e.sup.i.sup.∈E,.Math.GP(e.sub.i|U)  (Equation 3) for G=set of 4 geographic Comparison Fields and for e.sub.G=vector of 4 geographic fields Region, Metro, City, Zip
This equation is referred to as Equation 3, which is merely a special case of Equation 2, where the probability corresponding to e.sub.G is written out separately. This could be equivalently expressed accurately in the form of Equation 2, inserting e.sub.G as one of the e.sub.i.

(17) P(e.sub.G|U) can be defined in terms of its constituent fields, as shown in Equation 4 below:
P(e.sub.G|U)=P(e.sub.R|U)×P(e.sub.M|e.sub.R∩U)×P(e.sub.C|e.sub.M∩e.sub.R∩U)×P(e.sub.Z|e.sub.C∩e.sub.M∩e.sub.R∩U)  (Equation 4)
Definitions for the expansion of Equation 4 terms are shown below: e.sub.G=[e.sub.R, e.sub.M, e.sub.C, e.sub.Z] e.sub.R=1(DCM Region=TTD Region), a binary indicator of the Region fields in a Pair matching E.sub.M=1(DCM Metro=TTD Metro) e.sub.C=1(DCM City=TTD City) e.sub.Z=1(DCM Zip=TTD Zip) R=region value in a single Source Event M=metro value in a single Source Event C=city value in a single Source Event Z=zip value in a single Source Event RM=vector of region and metro values in a single Source Event, such as [California, San Francisco Bay Area] RMC=vector of region, metro and city values in a single Source Event, such as [California, San Francisco Bay Area, Emeryville] R2=vector containing the R for both Source Events region in a Pair, such as [California, Texas] RM2=vector containing the RM for both Source Events in a Pair, such as [California, San Francisco Bay Area, Texas, Dallas Ft. Worth] RMC2=vector containing the RMC for both Source Events in a Pair, such as [California, San Francisco Bay Area, Emeryville, Tex., Dallas Ft. Worth, Arlington] i.sub.k=where i indicates a pairwise vector such as RR, the value from the k.sup.th Set's Event comprising i, such as the DCM Source Event's R value in RR

(18) Expansion of Equation 4 terms is discussed below. First, P(e.sub.R|U) can be defined for two possible cases:

(19) $\begin{array}{cc}P\left(e_R=1.Math.U\right)=\underset{R:i=1}{\overset{n}{.Math.}}\underset{\mathrm{Set}:j=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}j\mathrm{with}R=i}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}j}\mathrm{for}n\mathrm{unique}\mathrm{values}\mathrm{of}R.& \mathrm{Case}\mathrm{A1}\\ P\left(e_R=0.Math.U\right)=1-P\left(e_R=1.Math.U\right)& \mathrm{Case}\mathrm{A2}\end{array}$
And P(e.sub.M|e.sub.R∩U) can be defined for 4 possible cases:

(20) $\begin{array}{cc}P\left(e_M=1.Math.e_R=1.Math.U\right)=\underset{R:i=1}{\overset{n}{.Math.}}\left[\frac{\#\mathrm{Pairs}\mathrm{with}{e}_R=1,R=i}{\#\mathrm{Pairs}\mathrm{with}{e}_R=1}\times \underset{M:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}R=i,M=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}R=i}\right]\mathrm{for}n\mathrm{unique}\mathrm{values}\mathrm{of}R;m\mathrm{unique}\mathrm{values}\mathrm{of}M.& \mathrm{Case}\mathrm{B1}\\ P\left(e_M=0.Math.e_R=1.Math.U\right)=1-P\left(e_M=1.Math.e_R=1.Math.U\right)& \mathrm{Case}\mathrm{B2}\\ P\left(e_M=1.Math.e_R=0.Math.U\right)=\underset{R:i=1}{\overset{n}{.Math.}}\left[\frac{\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\mathrm{RR}=i}{\#\mathrm{Pairs}\mathrm{with}{e}_R=0}\times \underset{M:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}R=i_k,M=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}R=i_k}\right]\mathrm{for}n\mathrm{unique}\mathrm{values}\mathrm{of}\mathrm{RR}\mathrm{in}\mathrm{pairs}\mathrm{with}{e}_R=0;m\mathrm{unique}\mathrm{values}\mathrm{of}M.& \mathrm{Case}\mathrm{B3}\\ P\left(e_M=0.Math.e_R=0.Math.U\right)=1-P\left(e_M=1.Math.e_R=0.Math.U\right)& \mathrm{Case}\mathrm{B4}\end{array}$
And P(e.sub.C|e.sub.R∩e.sub.M∩U) can be defined for 8 possible cases:

(21) $\begin{array}{cc}P\left(e_C=1.Math.e_R=1.Math.e_M=1.Math.U\right)=\underset{RM:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=1,\mathrm{RM}=i\end{array}}{\begin{array}{c}\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=1\end{array}}\times \underset{j=1}{\overset{m}{.Math.}}\underset{k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RM}=i,C=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RM}=i}\right]\mathrm{for}n\mathrm{unique}\mathrm{values}\mathrm{of}\mathrm{RM}\mathrm{in}\mathrm{Pairs}\mathrm{with}{e}_R=1,e_M=1;m\mathrm{unique}\mathrm{values}\mathrm{of}C.& \mathrm{Case}\mathrm{C1}\\ P\left(e_C=0.Math.e_R=1.Math.e_M=1.Math.U\right)=1-P\left(e_C=1.Math.e_R=1.Math.e_M=1.Math.U\right)1-P\left(e_C=1.Math.e_R=1.Math.e_M=1.Math.U\right)& \mathrm{Case}\mathrm{C2}\\ P\left(e_C=1.Math.e_R=1.Math.e_M=0.Math.U\right)=\underset{RM2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=0,\mathrm{RMRM}=i\end{array}}{\begin{array}{c}\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=0\end{array}}\times \underset{C:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMRM}=i,C=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMRM}=i}\right]& \mathrm{Case}\mathrm{C3}\\ P\left(e_C=0.Math.e_R=1.Math.e_M=0.Math.U\right)=1-P\left(e_C=1.Math.e_R=1.Math.e_M=0.Math.U\right)& \mathrm{Case}\mathrm{C4}\\ P\left(e_C=1.Math.e_R=0.Math.e_M=1.Math.U\right)=\underset{RM2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=1,\mathrm{RMRM}=i\end{array}}{\begin{array}{c}\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=1\end{array}}\times \underset{C:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMRM}=i,C=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMRM}=i}\right]& \mathrm{Case}\mathrm{C5}\\ P\left(e_C=0.Math.e_R=0.Math.e_M=1.Math.U\right)=1-P\left(e_C=1.Math.e_R=0.Math.e_M=1.Math.U\right)& \mathrm{Case}\mathrm{C6}\\ P\left(e_C=1.Math.e_R=0.Math.e_M=0.Math.U\right)=\underset{RM2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=0,\mathrm{RMRM}=i\end{array}}{\begin{array}{c}\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=0\end{array}}\times \underset{C:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMRM}=i,C=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMRM}=i}\right]& \mathrm{Case}\mathrm{C7}\\ P\left(e_C=0.Math.e_R=0.Math.e_M=0.Math.U\right)=1-P\left(e_C=1.Math.e_R=0.Math.e_M=0.Math.U\right)& \mathrm{Case}\mathrm{C8}\end{array}$

(22) In addition, P(e.sub.Z|e.sub.R∩e.sub.M∩e.sub.C∩U) defined for 16 possible cases:

(23) $\begin{array}{cc}P\left(e_Z=1.Math.e_R=1.Math.e_M=1.Math.e_C=1.Math.U\right)=\underset{RMC:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=1,e_C=1,\mathrm{RMC}=i\end{array}}{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=1,e_C=1\end{array}}\times \underset{Z:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i,Z=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i}\right]& \mathrm{Case}\mathrm{D1}\\ P\left(e_Z=0.Math.e_R=1.Math.e_M=1.Math.e_C=1.Math.U\right)=1-P\left(e_Z=1.Math.e_R=1.Math.e_M=1.Math.e_C=1.Math.U\right)& \mathrm{Case}\mathrm{D2}\\ P\left(e_Z=1.Math.e_R=0.Math.e_M=1.Math.e_C=1.Math.U\right)=\underset{RMC2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=1,e_C=1,\mathrm{RMC}2=i\end{array}}{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=1,e_C=1\end{array}}\times \underset{Z:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k,Z=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k}\right]& \mathrm{Case}\mathrm{D3}\\ P\left(e_Z=0.Math.e_R=0.Math.e_M=1.Math.e_C=1.Math.U\right)=1-P\left(e_Z=1.Math.e_R=0.Math.e_M=1.Math.e_C=1.Math.U\right)& \mathrm{Case}\mathrm{D4}\\ P\left(e_Z=1.Math.e_R=1.Math.e_M=0.Math.e_C=1.Math.U\right)=\underset{RMC2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=0,e_C=1,\mathrm{RMC}2=i\end{array}}{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=0,e_C=1\end{array}}\times \underset{Z:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k,Z=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k}\right]& \mathrm{Case}\mathrm{D5}\\ P\left(e_Z=0.Math.e_R=1.Math.e_M=0.Math.e_C=1.Math.U\right)=1-P\left(e_Z=1.Math.e_R=1.Math.e_M=0.Math.e_C=1.Math.U\right)& \mathrm{Case}\mathrm{D6}\\ P\left(e_Z=1.Math.e_R=1.Math.e_M=1.Math.e_C=0.Math.U\right)=\underset{RMC2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=1,e_C=0,\mathrm{RMC}2=i\end{array}}{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=1,e_C=0\end{array}}\times \underset{Z:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k,Z=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k}\right]& \mathrm{Case}\mathrm{D7}\\ P\left(e_Z=0.Math.e_R=1.Math.e_M=1.Math.e_C=0.Math.U\right)=1-P\left(e_Z=1.Math.e_R=1.Math.e_M=1.Math.e_C=0.Math.U\right)& \mathrm{Case}\mathrm{D8}\\ P\left(e_Z=1.Math.e_R=1.Math.e_M=0.Math.e_C=0.Math.U\right)=\underset{RMC2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=0,e_C=0,\mathrm{RMC}2=i\end{array}}{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=1,\\ e_M=0,e_C=0\end{array}}\times \underset{Z:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k,Z=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k}\right]& \mathrm{Case}\mathrm{D9}\\ P\left(e_Z=0.Math.e_R=1.Math.e_M=0.Math.e_C=1.Math.U\right)=1-P\left(e_Z=1.Math.e_R=1.Math.e_M=.Math.e_C=1.Math.U\right)& \mathrm{Case}\mathrm{D10}\\ P\left(e_Z=1.Math.e_R=0.Math.e_M=1.Math.e_C=0.Math.U\right)=\underset{RMC2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=1,e_C=0,\mathrm{RMC}2=i\end{array}}{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=1,e_C=0\end{array}}\times \underset{Z:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k,Z=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k}\right]& \mathrm{Case}\mathrm{D11}\\ P\left(e_Z=0.Math.e_R=0.Math.e_M=1.Math.e_C=0.Math.U\right)=1-P\left(e_Z=1.Math.e_R=0.Math.e_M=1.Math.e_C=0.Math.U\right)& \mathrm{Case}\mathrm{D12}\\ P\left(e_Z=1.Math.e_R=0.Math.e_M=0.Math.e_C=1.Math.U\right)=\underset{RMC2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=0,e_C=1,\mathrm{RMC}2=i\end{array}}{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=0,e_C=1\end{array}}\times \underset{Z:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k,Z=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k}\right]& \mathrm{Case}\mathrm{D13}\\ P\left(e_Z=0.Math.e_R=0.Math.e_M=0.Math.e_C=1.Math.U\right)=1-P\left(e_Z=1.Math.e_R=0.Math.e_M=0.Math.e_C=1.Math.U\right)& \mathrm{Case}\mathrm{D14}\\ P\left(e_Z=1.Math.e_R=0.Math.e_M=0.Math.e_C=0.Math.U\right)=\underset{RMC2:i=1}{\overset{n}{.Math.}}\left[\frac{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=0,e_C=0,\mathrm{RMC}2=i\end{array}}{\begin{array}{c}\#\mathrm{Pairs}\mathrm{with}{e}_R=0,\\ e_M=0,e_C=0\end{array}}\times \underset{Z:j=1}{\overset{m}{.Math.}}\underset{\mathrm{Set}:k=1}{\overset{2}{.Math.}}\frac{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k,Z=j}{\#\mathrm{Events}\mathrm{in}\mathrm{Set}k\mathrm{with}\mathrm{RMC}=i_k}\right]& \mathrm{Case}\mathrm{D15}\\ P\left(e_Z=0.Math.e_R=0.Math.e_M=0.Math.e_C=0.Math.U\right)=1-P\left(e_Z=1.Math.e_R=0.Math.e_M=0.Math.e_C=0.Math.U\right)& \mathrm{Case}\mathrm{D16}\end{array}$

(24) P(E.sub.G|U) can be calculated for each of 16 possible E.sub.G vectors by first creating a 16 row×10 column data structure PEgDf, as shown, for example below:

(25) TABLE-US-00001 EgIndex er em ec ez PrU PmrU PcrmU PzrmcU PEgU 1 1 1 1 1 A1 B1 C1 D1 2 1 1 1 0 A1 B1 C1 D2 3 1 1 0 1 A1 B1 C2 D3 4 1 1 0 0 A1 B1 C2 D4 5 1 0 1 1 A1 B2 C3 D5 6 1 0 1 0 A1 B2 C3 D6 7 1 0 0 1 A1 B2 C4 D7 8 1 0 0 0 A1 B2 C4 D8 9 0 1 1 1 A2 B3 C5 D9 10 0 1 1 0 A2 B3 C5 D10 11 0 1 0 1 A2 B3 C6 D11 12 0 1 0 0 A2 B3 C6 D12 13 0 0 1 1 A2 B4 C7 D13 14 0 0 1 0 A2 B4 C7 D14 15 0 0 0 1 A2 B4 C8 D15 16 0 0 0 0 A2 B4 C8 D16
The first five columns (EgIndex, er, em, ec, and ez) simply list out and index the sixteen possible combinations of the four binary variables that make up e.sub.G. The formulae for calculating the values that go in columns six through nine (PrU, PmrU, PcrmU, and PzrmcU) are provided above. The values provided in the table reference the appropriate equation from above that is used. For example, A1 refers to the equation provided in Case A1 above, while B4 refers to the equation provided in Case B4 discussed above. The last column equals the product of the values in columns six through nine. For the above calculations, P(e.sub.i=1|U) is defined for each Pair Field i as shown in Equation 5:

(26) $\begin{array}{cc}P\left(e_i=1.Math.U\right)=\underset{k=1}{\overset{n}{.Math.}}\mathrm{frequency}\mathrm{of}\mathrm{value}k\mathrm{in}\mathrm{source}\mathrm{set}1,\mathrm{field}i\times \mathrm{frequency}\mathrm{of}\mathrm{value}k\mathrm{in}\mathrm{source}\mathrm{set}2,\mathrm{field}i\mathrm{over}\mathrm{the}n\mathrm{unique}\mathrm{values}\mathrm{appearing}\mathrm{in}\mathrm{field}i\mathrm{over}\mathrm{both}\mathrm{source}\mathrm{sets}.& \left(\mathrm{Equation}5\right)\end{array}$

(27) P(U) is the probability of the Pair in question being an Unmatch, with no additional information or condition, with a frequentist approach. Over a large data set, this will equate to the number of real-world Match Pairs divided by the total number of Pairs considered. The number of un-matches in every unit group should be known because it is known that each source event belongs to exactly one Match Pair. Therefore:

(28) $P\left(U\right)=1-\frac{\mathrm{number}\mathrm{of}\mathrm{Matches}\mathrm{in}\mathrm{unit}\mathrm{group}}{\mathrm{number}\mathrm{of}\mathrm{Pairs}\mathrm{in}\mathrm{group}}=\frac{\mathrm{number}\mathrm{of}\mathrm{events}\mathrm{in}\mathrm{smaller}\mathrm{source}\mathrm{set}}{\begin{array}{c}\mathrm{number}\mathrm{of}\mathrm{events}\mathrm{in}\mathrm{smaller}\mathrm{source}\mathrm{set}\times \\ \mathrm{number}\mathrm{of}\mathrm{events}\mathrm{in}\mathrm{larg}\mathrm{er}\mathrm{source}\mathrm{set}\end{array}}=\frac{1}{\mathrm{number}\mathrm{of}\mathrm{events}\mathrm{in}\mathrm{larg}\mathrm{er}\mathrm{source}\mathrm{set}}$

(29) The above Bayesian inference allows for the calculation of a probability of Match for an individual Pair based solely on the row of Pair Fields corresponding to the two events that make up that Pair. The probability value it produces (P1) is the best estimate based solely on that information. It is understood, however, that for each event from the smaller Source Set, precisely one Pair including that event will be a Match in the real-world sense (the set of all such Pairs including the same event may be referred to as a “Pair Cohort”). Therefore:

(30) $\underset{j=1}{\overset{n}{.Math.}}P\left({\mathrm{pair}}_{i,j}\mathrm{is}\mathrm{Match}\right)=1$$\mathrm{for}\{\begin{array}{c}{\mathrm{pair}}_{i,j}=\mathrm{the}\mathrm{pair}\mathrm{of}\mathrm{Event}i\mathrm{from}\mathrm{small}\mathrm{Source}\mathrm{Set}\mathrm{and}\mathrm{Event}j\mathrm{from}\mathrm{large}\mathrm{Source}\mathrm{Set}\\ i=\mathrm{indicator}\mathrm{of}\mathrm{single}\mathrm{event}\mathrm{from}\mathrm{smalller}\mathrm{Source}\mathrm{Set}\\ n=\mathrm{number}\mathrm{of}\mathrm{Events}\mathrm{in}\mathrm{larger}\mathrm{Source}\mathrm{Set}\end{array}$
This property is reflected in part in the prior probability P(H)=P(M)=P3 in the Bayesian analysis. The Bayesian analysis does not reflect, however, that precisely one of the Pairs corresponding to each Event is a Match and all of the others are not. The single row for each Event demonstrating the highest P1 value can be selected and designated as the single Match among all rows corresponding to that Event. More precisely, the probability measure can be calculated with the following equation
P1*=P(M|P1 and precisely one pair is M for all Pairs incorporating a single Event)
This value equals the following, referred to as Equation 6:

(31) 0$\frac{P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)}{\begin{array}{c}P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)+\\ \underset{j\ne i}{.Math.}(P{1}_j\times \underset{k\ne j}{.Math.}〚\left(1-P{1}_k\right))〛\end{array}}=P{1}_i\times \frac{\underset{j\ne i}{.Math.}\left(1-P{1}_j\right)}{\begin{array}{c}P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)+\\ \underset{j\ne i}{.Math.}(P{1}_j\times \underset{k\ne j}{.Math.}〚\left(1-P{1}_k\right))〛\end{array}}=P{1}_i^{*}.$
where P1.sub.i is the P1 value of the Pair in question, j≠i denotes all Pairs in the same Pair Cohort as Pair i other than Pair i, and k≠j denotes all Pairs in the same Pair Cohort as Pair i other than Pair j and including Pair i.

(32) This is the probability of the state that the given Pair is a Match, by P1, while all other Pairs including the given event from the smaller source set are Unmatch, also by P1, as a proportion of the state space that is the sum of all states where exactly one Pair from the Pair Cohort is a Match. Within each Pair Cohort, P1* values will migrate toward 1 and 0 from P1 values, which will make Match pairs stand out (they will migrate toward 1 while all other pairs migrate toward 0), and will make determining when errors in the data exclude a Match for a given event (because P1* for the “strongest” candidate pair in a Pair Cohort will not migrate toward 1 as strongly as expected).

(33) The quantity

(34) $\frac{\underset{j\ne i}{.Math.}\left(1-P{1}_j\right)}{P{1}_i\times \underset{j\ne i}{.Math.}\left(1-P{1}_j\right)+\underset{j\ne i}{.Math.}(P{1}_j\times \underset{k\ne j}{.Math.}〚\left(1-P{1}_k\right))〛}$
from Equation 6 may be referred to as the “Sole Rightful Heir Factor” and it can be simplified as:
(Π_(j≠i)(1−P1_j))/(Σ_(l=1){circumflex over ( )}nP1_l×Π_(m≠l)(1−P1_m)))
where j≠i still denotes all Pairs in Pair i's Pair Cohort other than Pair i, n is the total number of Pairs in the Pair Cohort, l is the index for all Pairs in such Pair Cohort.

(35) The above calculation gives a probability value for each Pair being a Match, but it must be determined what level of such probability should cause such Pair to be treated as a Match versus an Unmatch. Such level is called the “Decision Threshold.” The migration of P1* toward extreme values will enhance the ability to select a reliable Decision Threshold by creating a wider “street” separating “high” P1* values for each Small Source event from “low” values. A simple supervised clustering classification model like K-means, trained on the P1* values, will thus produce a robust boundary between such values and allow determination of a confidence level in the Match and Unmatch determinations.

(36) It may be understood that the present invention as described above may be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art may know and appreciate other ways and/or methods to implement the present invention using hardware, software, or a combination of hardware and software.

(37) The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.

(38) One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention. A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary. Recitation of “and/or” is intended to represent the most inclusive sense of the term unless specifically indicated to the contrary.

(39) One or more of the elements of the present system may be claimed as means for accomplishing a particular function. Where such means-plus-function elements are used to describe certain elements of a claimed system it will be understood by those of ordinary skill in the art having the present specification, figures and claims before them, that the corresponding structure is a general purpose computer, processor, or microprocessor (as the case may be) programmed to perform the particularly recited function using functionality found in any general purpose computer without special programming and/or by implementing one or more algorithms to achieve the recited functionality. As would be understood by those of ordinary skill in the art that algorithm may be expressed within this disclosure as a mathematical formula, a flow chart, a narrative, and/or in any other manner that provides sufficient structure for those of ordinary skill in the art to implement the recited process and its equivalents.

(40) While the present disclosure may be embodied in many different forms, the drawings and discussion are presented with the understanding that the present disclosure is an exemplification of the principles of one or more inventions and is not intended to limit any one of the inventions to the embodiments illustrated.

(41) Further advantages and modifications of the above described system and method will readily occur to those skilled in the art. The disclosure, in its broader aspects, is therefore not limited to the specific details, representative system and methods, and illustrative examples shown and described above. Various modifications and variations can be made to the above specification without departing from the scope or spirit of the present disclosure, and it is intended that the present disclosure covers all such modifications and variations provided they come within the scope of the following claims and their equivalents.