Triple
T21696039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Collaboration with Research Councils |
E535516
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research administration unit |
C1214
|
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 administration unit Context triple: [Centre for Collaboration with Research Councils, instanceOf, research administration unit]
-
A.
research administration office
chosen
A research administration office is an organizational unit that supports and oversees the planning, funding, compliance, and management of research activities within an institution.
-
B.
university administrative unit
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
-
C.
research ministry
A research ministry is a governmental or organizational body responsible for overseeing, funding, and guiding scientific and technological research to support policy, innovation, and societal development.
-
D.
academic research department
An academic research department is an organizational unit within an educational or research institution that coordinates faculty, students, and resources to conduct specialized scholarly inquiry and produce new knowledge in a particular discipline or field.
-
E.
research committee
A research committee is a group of appointed individuals responsible for evaluating, guiding, and overseeing research activities, proposals, and policies within an organization or institution.
- 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.