Triple
T5171117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Center for Visual Science |
E116679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multidisciplinary research center |
C11789
|
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: multidisciplinary research center Context triple: [Center for Visual Science, instanceOf, multidisciplinary research center]
-
A.
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.
-
B.
public research institution
A public research institution is a government-funded organization dedicated to advancing knowledge and innovation through systematic investigation, experimentation, and dissemination of findings for the benefit of society.
-
C.
research and engagement centre
chosen
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.
-
D.
center of excellence
A center of excellence is a dedicated organizational unit that concentrates specialized expertise, best practices, and resources to drive high-quality performance and continuous improvement in a specific domain.
-
E.
multidisciplinary framework
A multidisciplinary framework is an integrated structure that combines theories, methods, and perspectives from multiple academic or professional fields to address complex problems more comprehensively.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:45 p.m.