Triple
T30339472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornell Chimes |
E771707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cornell University tradition |
C2293
|
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: Cornell University tradition Context triple: [Cornell Chimes, instanceOf, Cornell University tradition]
-
A.
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.
-
B.
Cornell University unit
A Cornell University unit is an organizational entity within Cornell, such as a college, school, department, or administrative office, that carries out specific academic, research, or support functions for the institution.
-
C.
college of Cornell University
A college of Cornell University is a semi-autonomous academic division within the university that organizes related departments and programs to offer specialized undergraduate and/or graduate education and conduct research in a particular field or set of disciplines.
-
D.
Columbia University school
A Columbia University school is an academic division within Columbia University that offers specialized undergraduate, graduate, and professional programs, each with its own faculty, curriculum, and administrative structure.
-
E.
university tradition
chosen
A university tradition is a recurring, institution-specific practice or ritual that embodies the shared history, values, and identity of a university community.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:55 p.m.