Triple
T13999428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Industrial Consultancy and Sponsored Research |
E336783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research administration centre |
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 centre Context triple: [Centre for Industrial Consultancy and Sponsored Research, instanceOf, research administration centre]
-
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.
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.
-
C.
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.
-
D.
research and engagement centre
A research and engagement centre is an institution that conducts systematic inquiry into specific fields while actively collaborating with and involving stakeholders or communities to apply, share, and co-create knowledge.
-
E.
research center program
A research center program is an organized initiative within a research institution that coordinates projects, resources, and collaborations to advance inquiry and innovation in a specific field or set of related disciplines.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:19 p.m.