Triple
T2208425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LHC Run 3 |
E50856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | LHC data-taking period |
C7094
|
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: LHC data-taking period Context triple: [LHC Run 3, instanceOf, LHC data-taking period]
-
A.
LHC run
chosen
An LHC run is a defined operational period of the Large Hadron Collider during which proton or ion beams are circulated and collided under specific energy and luminosity conditions to collect experimental data.
-
B.
operational period of the Large Hadron Collider
The operational period of the Large Hadron Collider is the span of time during which the accelerator is actively running experiments, colliding particles, and collecting data under defined technical and safety conditions.
-
C.
high-energy physics data-taking run
A high-energy physics data-taking run is a defined period during which a particle detector records collision events under stable experimental conditions to collect data for later analysis.
-
D.
CERN experiment
A CERN experiment is a large-scale, collaborative scientific investigation conducted at CERN’s particle physics facilities to study fundamental particles and forces using high-energy collisions and advanced detectors.
-
E.
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.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:46 p.m.