Triple
T17764500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWAKE Run 2 experiments |
E443468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | plasma wakefield acceleration experiment |
C19460
|
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: plasma wakefield acceleration experiment Context triple: [AWAKE Run 2 experiments, instanceOf, plasma wakefield acceleration experiment]
-
A.
particle accelerator experiment
chosen
A particle accelerator experiment is a scientific setup in which charged particles are accelerated to high energies and collided with targets or other particles to study fundamental forces, particles, and the structure of matter.
-
B.
linear particle accelerator
A linear particle accelerator is a device that uses oscillating electric fields along a straight path to accelerate charged particles to high speeds for research, medical, or industrial applications.
-
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 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.
-
E.
particle accelerator
A particle accelerator is a machine that uses electromagnetic fields to propel charged particles to high speeds and direct them into beams for research, medical, or industrial applications.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:11 a.m.