Triple
T25030781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WISTA Science and Technology Park |
E626836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and business hub |
C49712
|
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 business hub Context triple: [WISTA Science and Technology Park, instanceOf, research and business hub]
-
A.
research and education hub
A research and education hub is a centralized environment where scholars, students, and professionals collaborate to generate new knowledge, share resources, and engage in learning and innovation.
-
B.
interdisciplinary hub
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.
-
C.
research and competence centre
A research and competence centre is an organizational unit that conducts advanced studies and develops, concentrates, and disseminates specialized expertise within a particular field to support innovation, education, and practical application.
-
D.
research and education centre
A research and education centre is an institution dedicated to generating new knowledge through systematic investigation and disseminating it through structured teaching, training, and outreach 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. chosen
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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:07 a.m.