Triple
T24797480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thun campus |
E620427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and innovation site |
C49561
|
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 innovation site Context triple: [Thun campus, instanceOf, research and innovation site]
-
A.
research and innovation cluster
A research and innovation cluster is a geographically or virtually concentrated network of organizations, institutions, and individuals that collaborate to generate new knowledge, technologies, and solutions, driving competitive advantage and regional development.
-
B.
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.
-
C.
innovation and knowledge centre
An innovation and knowledge centre is a collaborative hub that integrates research, expertise, and resources to develop, share, and apply new ideas, technologies, and best practices.
-
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 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.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:48 a.m.