Triple
T21692744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Health Data |
E535411
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research infrastructure unit |
C13835
|
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 unit Context triple: [Centre for Health Data, instanceOf, research infrastructure unit]
-
A.
research infrastructure component
A research infrastructure component is a foundational hardware, software, or service element that supports the collection, storage, processing, and sharing of data and tools necessary for conducting and advancing research.
-
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.
research infrastructure collection
chosen
A research infrastructure collection is an organized set of facilities, equipment, data, and services that together support and enable systematic scientific investigation and innovation.
-
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.
multidisciplinary research unit
A multidisciplinary research unit is an organized group that integrates expertise, methods, and perspectives from multiple academic or professional fields to collaboratively investigate complex problems and generate comprehensive insights.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:45 p.m.