Triple
T9863620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutgers Biomedical and Health Sciences |
E239776
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of Rutgers University |
C26562
|
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: division of Rutgers University Context triple: [Rutgers Biomedical and Health Sciences, instanceOf, division of Rutgers University]
-
A.
division of Columbia University
A division of Columbia University is an organizational unit within the institution, such as a school, college, or department, that administers specific academic programs, research activities, and related services.
-
B.
Rutgers University tradition
A Rutgers University tradition is a recurring, community-valued practice or ritual—often tied to campus history, events, or symbols—that fosters shared identity and continuity among Rutgers students, alumni, and affiliates.
-
C.
Rutgers University building
A Rutgers University building is a physical structure located on one of Rutgers’ campuses that houses academic, administrative, research, residential, or student-life functions associated with the university.
-
D.
division of the University of California
A division of the University of California is an organizational unit within the UC system that groups related academic departments, programs, or administrative functions under a common leadership and mission.
-
E.
Rutgers University symbol
The Rutgers University symbol is the official visual emblem representing Rutgers University’s identity, heritage, and institutional values across communications and branding.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:35 p.m.