Triple
T14991484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDF Collaboration |
E373844
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | particle physics experiment collaboration |
C13497
|
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 experiment collaboration Context triple: [CDF Collaboration, instanceOf, particle physics experiment collaboration]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Fermilab experiment
chosen
A Fermilab experiment is a high-energy physics research project conducted at the Fermi National Accelerator Laboratory to investigate fundamental particles, forces, and the structure of matter using particle accelerators and detectors.
-
E.
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.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:53 a.m.