Triple
T21989233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALEPH Collaboration |
E543040
|
entity |
| Predicate | abbreviationFor |
P43
|
FINISHED |
| Object | Apparatus for LEP Physics |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Apparatus for LEP Physics Context triple: [ALEPH Collaboration, abbreviationFor, Apparatus for LEP Physics]
-
A.
Apparatus for LEP Physics
chosen
Apparatus for LEP Physics (ALEPH) was a major particle detector experiment at CERN’s Large Electron–Positron Collider designed to study high-energy electron-positron collisions and probe the Standard Model of particle physics.
-
B.
Mu2e experiment
The Mu2e experiment is a high-energy physics project at Fermilab designed to search for the extremely rare conversion of muons into electrons without neutrinos, probing physics beyond the Standard Model.
-
C.
CERN experimental programme
The CERN experimental programme is the coordinated set of particle physics experiments and research activities conducted at CERN’s accelerators and facilities to investigate the fundamental constituents and forces of nature.
-
D.
LHC detector R&D
LHC detector R&D is the program of research and development focused on designing, testing, and improving particle detectors for experiments at the Large Hadron Collider.
-
E.
Apparatus for Meson and Baryon Experimental Research
Apparatus for Meson and Baryon Experimental Research is a high-energy physics experiment designed to study the properties and interactions of mesons and baryons using particle beams and advanced detectors.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:05 p.m.