Triple
T22813801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPS North Area |
E565049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fixed-target experimental area |
C7109
|
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: fixed-target experimental area Context triple: [SPS North Area, instanceOf, fixed-target experimental area]
-
A.
fixed-target particle physics experiment
A fixed-target particle physics experiment is a setup where a beam of accelerated particles is directed onto a stationary target to study the resulting interactions and reveal fundamental properties of matter and forces.
-
B.
experimental area
chosen
An experimental area is a designated space equipped and organized for conducting controlled tests, trials, or research activities under specified conditions.
-
C.
accelerator interaction region
An accelerator interaction region is the specially designed section of a particle accelerator where beams are brought into collision or close proximity for experiments and detector measurements.
-
D.
particle beam test facility
A particle beam test facility is a specialized laboratory that generates and delivers controlled beams of particles (such as electrons, protons, or ions) for testing, calibrating, and characterizing detectors, materials, and accelerator components.
-
E.
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.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:32 p.m.