As @jgo points out, there are multiple inspectors that could give this info that pull from different sources, and not all sources are available on all platforms.
This is one option:
sums of threads of cpupackages
But that seems to only count the threads of a single CPU package. The right answer might actually be this if there are multiple CPUs:
(count of cpupackage * it) of sums of threads of cpupackages
It is hard for me to test some of these inspectors because I don’t have a lot of test systems lying around with multiple physical CPUs.
It should also be possible to read this info using the DMI/SMBIOS inspectors. On windows, the WMI inspectors should also work. On Mac, the IO Kit Registry should have this same info.
Another option you could do to confirm the results of the inspectors is to use a command that should return the correct results you expect and run that with bigfix, output the results to a file, and read that back with relevance. This is not an ideal solution, particularly for all computers, but it is a useful validation method you could use on select systems to directly compare the different options available directly with Relevance inspectors to what you see as the correct count based upon running a command. You can use this to then be more confident of the direct relevance results elsewhere.
Based upon the testing I just did, it doesn’t seem like this info is available in SMBIOS, at least not on my test system, which surprised me:
unique values of (it as string) of ((name of it | ""), ( (name of it | "") & " : " & (it as string | "")) of values of it) of structures of smbios
This relevance should return a mostly exhaustive list of what is available in SMBIOS.
At least for my VM, the number of “CPU socket” returned was way higher than the number of CPUs / Threads.