Triple
T794604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Engineering and Public Policy (Carnegie Mellon University) |
E16991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdisciplinary department |
C57
|
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 department Context triple: [Department of Engineering and Public Policy (Carnegie Mellon University), instanceOf, interdisciplinary department]
-
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 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.
-
C.
academic division
chosen
An academic division is a major organizational unit within an educational institution that groups related departments, programs, or disciplines under a common administrative and academic structure.
-
D.
college within a university
A college within a university is a semi-autonomous academic division that groups related disciplines, manages specific degree programs, and oversees faculty and resources within its subject area.
-
E.
academic discipline
An academic discipline is a branch of knowledge with a defined subject matter, methods, and community of scholars that structures research, teaching, and professional practice.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.