Triple
T3616142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muon g-2 experiment |
E76604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | muon magnetic moment 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 magnetic moment experiment Context triple: [Muon g-2 experiment, instanceOf, muon magnetic moment experiment]
-
A.
CERN experiment
A CERN experiment is a large-scale, collaborative scientific investigation conducted at CERN’s particle physics facilities to study fundamental particles and forces using high-energy collisions and advanced detectors.
-
B.
kaon decay experiment
A kaon decay experiment is a particle physics study that produces and observes kaons to measure their decay modes, lifetimes, and symmetry-violating processes, testing the predictions of the Standard Model.
-
C.
operational period of the Large Hadron Collider
The operational period of the Large Hadron Collider is the span of time during which the accelerator is actively running experiments, colliding particles, and collecting data under defined technical and safety conditions.
-
D.
LHC run
An LHC run is a defined operational period of the Large Hadron Collider during which proton or ion beams are circulated and collided under specific energy and luminosity conditions to collect experimental data.
-
E.
particle accelerator upgrade project
A particle accelerator upgrade project is a coordinated engineering and scientific effort to enhance an existing accelerator’s performance, capabilities, or reliability through targeted hardware, software, and infrastructure improvements.
- F. None of above. chosen
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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:23 p.m.