Triple
T23138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Science and Technology Centers |
E460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdisciplinary research hubs |
C182
|
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: interdisciplinary research hubs Context triple: [Science and Technology Centers, instanceOf, interdisciplinary research hubs]
-
A.
interdisciplinary hub
chosen
An interdisciplinary hub is a collaborative space—physical or virtual—where experts from diverse fields converge to share knowledge, integrate methods, and co-create innovative solutions to complex problems.
-
B.
university collaboration
University collaboration is the structured partnership between universities and external entities (such as other academic institutions, industry, government, or communities) to jointly pursue research, education, innovation, and resource sharing.
-
C.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
D.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
-
E.
research and development organization
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.