Triple
T14991251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brookhaven E821 experiment |
E373839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | muon g-2 experiment |
C13494
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: muon g-2 experiment Context triple: [Brookhaven E821 experiment, instanceOf, muon g-2 experiment]
-
A.
muon magnetic moment experiment
chosen
A muon magnetic moment experiment precisely measures how the muon's intrinsic magnetic dipole deviates from the value predicted by the Standard Model, providing a sensitive test for new physics.
-
B.
antihydrogen experiment
An antihydrogen experiment is a scientific investigation that creates, traps, and studies antihydrogen atoms to test fundamental symmetries and compare the properties of matter and antimatter.
-
C.
Fermilab experiment
A Fermilab experiment is a high-energy physics research project conducted at the Fermi National Accelerator Laboratory to investigate fundamental particles, forces, and the structure of matter using particle accelerators and detectors.
-
D.
Tevatron experiment
A Tevatron experiment is a high-energy particle physics investigation conducted using the Tevatron proton–antiproton collider at Fermilab to study fundamental particles and forces.
-
E.
CPT symmetry test experiment
A CPT symmetry test experiment is a precise measurement setup designed to compare the properties of particles and antiparticles (or processes and their CPT-conjugates) to verify the fundamental invariance of physical laws under the combined operations of charge conjugation (C), parity transformation (P), and time reversal (T).
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:53 a.m.