Triple
T21575339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eranos conferences |
E532380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdisciplinary symposium |
C45004
|
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 symposium Context triple: [Eranos conferences, instanceOf, interdisciplinary symposium]
-
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.
interdisciplinary program
An interdisciplinary program is an academic course of study that integrates methods, perspectives, and content from multiple disciplines to address complex questions or problems that cannot be fully understood through a single field alone.
-
D.
biennial conference
A biennial conference is a large, organized gathering of participants held every two years to share knowledge, present research, and foster collaboration within a specific field or community.
-
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. 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:30 p.m.