Triple
T7457456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgman seal |
E172162
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | experimental physics apparatus component |
C4752
|
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: experimental physics apparatus component Context triple: [Bridgman seal, instanceOf, experimental physics apparatus component]
-
A.
experimental apparatus
chosen
An experimental apparatus is a physical setup or device designed and assembled to conduct controlled scientific investigations, measurements, or tests.
-
B.
physics experiment
A physics experiment is a controlled procedure designed to test hypotheses, observe phenomena, and measure physical quantities to understand the laws governing the natural world.
-
C.
experimental physicist
An experimental physicist is a scientist who designs and conducts experiments to test physical theories, measure phenomena, and discover new laws of nature using specialized instruments and data analysis.
-
D.
CERN accelerator complex component
A CERN accelerator complex component is a specialized physical or control-system element—such as magnets, RF cavities, beamlines, detectors, or power and cooling infrastructure—that collectively enables the production, acceleration, steering, and monitoring of particle beams for experimental research.
-
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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:15 p.m.