Triple
T36165336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statewide Programs and Institutes |
E1045982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and outreach units |
C52867
|
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 and outreach units Context triple: [Statewide Programs and Institutes, instanceOf, research and outreach units]
-
A.
research and collaboration unit
A research and collaboration unit is an organizational entity that coordinates and conducts systematic inquiry while facilitating partnerships and knowledge exchange among internal and external stakeholders.
-
B.
research collaboration unit
A research collaboration unit is an organizational entity that coordinates and supports joint research activities among multiple investigators, departments, or institutions to achieve shared scientific goals.
-
C.
Research unit
chosen
A research unit is an organized group within an institution dedicated to conducting systematic investigations, generating new knowledge, and supporting scholarly or scientific inquiry in specific fields or interdisciplinary areas.
-
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.
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.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.