The data analysed in this work were collected between 2010 and 2018 during the LHC Run 1 and Run 2 data taking periods.
They comprise pp, p==Pb, Xe==Xe, and Pb==Pb collisions at centre-of-mass energies per nucleon pair ranging from \({\sqrt{s_\mathrm {NN}\,} = 2.76}\)  up to 13\(~\mathrm {TeV}\) .
Hadronic collisions were selected with two different minimum-bias (MB) interaction triggers.
In Run 1, a single hit in either of V0A or V0C detectors or in the SPD was required (denoted as V0OR) in coincidence with a crossing of two particle bunches in the LHC at the nominal ALICE interaction point.
For the Run 2 data taking period, a signal in both V0A and V0C was necessary to fulfil the MB trigger condition (denoted V0AND).
Therefore, the former is also sensitive to single diffractive pp events while the latter almost exclusively selects non-single diffractive interactions.
The offline event selection (for details see Ref. [1]}, [2]}) is optimised to reject beam-induced background and pileup collisions.
Events with no reconstructed vertex and those with poor vertex resolution are rejected.
Both the trigger efficiency and the vertex requirements affect mostly low multiplicity events.
To ensure full pseudorapidity coverage of the tracking detectors (in particular by the inner ITS layers) and therefore avoid a possible asymmetry in the kinematic selection of the tracks, all collisions are required to have their reconstructed primary vertex located within \({\left| V^\mathrm {meas}_\mathrm {z} \right| < 10~\text{cm}}\)  along the beam direction with respect to the nominal interaction point.
Table REF  shows an overview of the data sets and their corresponding number of events selected for this analysis.
<TABLE>