Triple
T31944067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Particle Data Group reports |
E815599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | compilation of particle physics data |
C61412
|
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: compilation of particle physics data Context triple: [Particle Data Group reports, instanceOf, compilation of particle physics data]
-
A.
particle physics experiment program
A particle physics experiment program is a coordinated set of software tools, data acquisition systems, and analysis workflows designed to plan, run, and interpret high-energy physics experiments.
-
B.
particle physics collaboration
A particle physics collaboration is a large, often international team of scientists, engineers, and institutions that jointly design, build, operate, and analyze experiments to study fundamental particles and their interactions.
-
C.
B-physics experiment
A B-physics experiment is a particle physics study focused on producing and analyzing B mesons to investigate flavor physics, CP violation, and potential physics beyond the Standard Model.
-
D.
Tevatron experiment
A Tevatron experiment is a high-energy particle physics investigation conducted using the Tevatron proton–antiproton collider at Fermilab to study fundamental particles and forces.
-
E.
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.
- F. None of above. chosen
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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:06 a.m.