Triple
T6294993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Science Research Initiative |
E141108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdisciplinary research initiative |
C6661
|
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 initiative Context triple: [Web Science Research Initiative, instanceOf, interdisciplinary research initiative]
-
A.
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.
-
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 initiative
chosen
A research initiative is a coordinated, goal-driven effort to investigate specific questions or problems, typically organized around a defined scope, methodology, timeline, and set of expected outcomes.
-
D.
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.
-
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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:27 p.m.