Triple
T8926803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statistical Research Group at Columbia University |
E212556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdisciplinary team |
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 team Context triple: [Statistical Research Group at Columbia University, instanceOf, interdisciplinary team]
-
A.
multidisciplinary planning team
A multidisciplinary planning team is a collaborative group of professionals from diverse fields who jointly design, coordinate, and optimize complex projects or initiatives.
-
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 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.
-
D.
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.
-
E.
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.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:57 p.m.