Triple
T34616350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermilab fixed-target program |
E888875
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fixed-target experiment program |
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: fixed-target experiment program Context triple: [Fermilab fixed-target program, instanceOf, fixed-target experiment program]
-
A.
fixed-target particle physics experiment
A fixed-target particle physics experiment is a setup where a beam of accelerated particles is directed onto a stationary target to study the resulting interactions and reveal fundamental properties of matter and forces.
-
B.
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.
-
C.
nuclear physics experiment program
A nuclear physics experiment program is a coordinated set of experiments, instrumentation, data acquisition, and analysis activities designed to investigate the properties, interactions, and structure of atomic nuclei under controlled laboratory conditions.
-
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.
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.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.