Triple
T33908906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute of Research Management and Services, University of Malaya |
E869259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research management office |
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 management office Context triple: [Institute of Research Management and Services, University of Malaya, instanceOf, research management office]
-
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 management centre
A research management centre is an organizational unit that coordinates, supports, and oversees the planning, funding, administration, and compliance of research activities within an institution.
-
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.
research support unit
A research support unit is an organizational entity that provides specialized services, resources, and expertise to facilitate, coordinate, and enhance the planning, execution, and dissemination of research activities.
-
E.
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.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.