Triple
T24716888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interdisciplinary Research Collaboratory |
E612185
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research support center |
C45180
|
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 support center Context triple: [Interdisciplinary Research Collaboratory, instanceOf, research support center]
-
A.
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.
-
B.
research support community
A research support community is a collaborative network of individuals and resources that provides guidance, feedback, tools, and encouragement to help researchers conduct, improve, and share their work.
-
C.
research library
A research library is a specialized institution that collects, organizes, preserves, and provides access to scholarly resources and reference services to support advanced study and original research.
-
D.
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.
-
E.
research coordination centre
chosen
A research coordination centre is an organizational hub that plans, integrates, and supports the activities, communication, and resources of multiple research projects or institutions to ensure efficient, aligned, and high-quality scientific work.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 3:38 a.m.