Triple
T17713374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERN observer states |
E441625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CERN status category |
C39582
|
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: CERN status category Context triple: [CERN observer states, instanceOf, CERN status category]
-
A.
CERN governance category
A CERN governance category is a classification that defines the roles, responsibilities, and decision-making authority of organizational bodies within CERN’s institutional and administrative structure.
-
B.
CERN organizational unit
A CERN organizational unit is a defined structural entity within CERN, such as a department, group, or section, responsible for specific scientific, technical, or administrative functions and reporting lines.
-
C.
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.
-
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.
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.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:06 a.m.