Triple
T6146552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H8 beam line |
E137092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | particle physics beam 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: particle physics beam line Context triple: [H8 beam line, instanceOf, particle physics beam 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 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.
-
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 complex
A particle accelerator complex is an integrated facility comprising accelerators, beamlines, detectors, and support infrastructure designed to accelerate charged particles to high energies for research, medical, or industrial applications.
-
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.
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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:16 p.m.