Triple
T21575390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jungian circle at Eranos |
E532381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdisciplinary research community |
C2520
|
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 community Context triple: [Jungian circle at Eranos, instanceOf, interdisciplinary research community]
-
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.
interdisciplinary work
Interdisciplinary work is collaborative activity that integrates methods, perspectives, and knowledge from multiple academic or professional fields to address complex questions or problems that cannot be fully understood within a single discipline.
-
C.
multidisciplinary research unit
A multidisciplinary research unit is an organized group that integrates expertise, methods, and perspectives from multiple academic or professional fields to collaboratively investigate complex problems and generate comprehensive insights.
-
D.
intellectual community
chosen
An intellectual community is a group of individuals who share, develop, and critically engage with ideas, knowledge, and inquiry around common interests or disciplines.
-
E.
research support community
A research support community is a collaborative network of individuals and resources that provides guidance, feedback, tools, and encouragement to help researchers conduct, improve, and share their work.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:30 p.m.