Triple
T14547508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPIC Handle Service |
E341326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research infrastructure component |
C34934
|
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: research infrastructure component Context triple: [EPIC Handle Service, instanceOf, research infrastructure component]
-
A.
research infrastructure collection
A research infrastructure collection is an organized set of facilities, equipment, data, and services that together support and enable systematic scientific investigation and innovation.
-
B.
research facility
A research facility is a specialized institution equipped with laboratories, instruments, and resources where scientists and experts systematically investigate, experiment, and develop new knowledge or technologies.
-
C.
R infrastructure component
An R infrastructure component is a foundational element—such as runtime, package system, or tooling—that supports the execution, management, and scalability of R-based data analysis and applications.
-
D.
research facility area
A research facility area is a designated space within or associated with a research institution where scientific, technical, or experimental activities are conducted, supported, or managed.
-
E.
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.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.