Triple
T22984542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H2 beam line |
E571567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | experimental beam transport line |
C6336
|
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: experimental beam transport line Context triple: [H2 beam line, instanceOf, experimental beam transport line]
-
A.
particle beam line
chosen
A particle beam line is an engineered pathway of magnets, vacuum tubes, and diagnostic devices that transports, focuses, and shapes a stream of charged particles from a source to experimental or application targets.
-
B.
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.
-
C.
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.
-
D.
particle accelerator experiment
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.
-
E.
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.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:49 p.m.