Triple
T32290142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BiD |
E824943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdisciplinary research group |
C20764
|
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 group Context triple: [BiD, instanceOf, interdisciplinary research group]
-
A.
multidisciplinary research unit
chosen
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.
-
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.
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.
-
D.
university research team
A university research team is a collaborative group of faculty, students, and sometimes external partners who systematically investigate specific academic or scientific questions to generate new knowledge and publish their findings.
-
E.
research team
A research team is a collaborative group of individuals with complementary expertise who systematically investigate questions or problems to generate new knowledge or solutions.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:44 a.m.