Triple
T21853883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Neural Computation |
E539572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neuroscience research organization |
C12533
|
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: neuroscience research organization Context triple: [Centre for Neural Computation, instanceOf, neuroscience research organization]
-
A.
neuroscience research unit
A neuroscience research unit is a specialized organizational entity dedicated to investigating the structure, function, and disorders of the nervous system through experimental, computational, and translational studies.
-
B.
neurosciences institute
chosen
A neurosciences institute is a specialized research and clinical organization dedicated to studying the nervous system, brain function, and related disorders to advance understanding, diagnosis, and treatment.
-
C.
neuroscience research program
A neuroscience research program is an organized, long-term scientific initiative that systematically investigates the structure, function, and development of the nervous system to advance understanding of brain and behavior.
-
D.
brain health research organization
A brain health research organization is an entity dedicated to studying the brain and nervous system to advance understanding, prevention, diagnosis, and treatment of neurological and mental health conditions.
-
E.
neuroscience department
A neuroscience department is an academic or research unit dedicated to studying the structure, function, development, and disorders of the nervous system through interdisciplinary scientific approaches.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 6:56 p.m.