Triple
T24916347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HERA |
E623995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electron–proton collider |
C1691
|
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: electron–proton collider Context triple: [HERA, instanceOf, electron–proton collider]
-
A.
hadron collider
A hadron collider is a type of particle accelerator that propels hadrons, such as protons or heavy ions, to extremely high energies and smashes them together to study fundamental particles and forces.
-
B.
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.
-
C.
particle accelerator
chosen
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.
-
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 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.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:28 a.m.