Triple
T3629012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale School of Architecture |
E76908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic division of Yale University |
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: academic division of Yale University Context triple: [Yale School of Architecture, instanceOf, academic division of Yale University]
-
A.
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.
-
B.
Yale University organization
A Yale University organization is a formally recognized group or entity within Yale that brings together students, faculty, staff, or alumni around shared academic, professional, cultural, social, or service-oriented interests and activities.
-
C.
Yale University building
A Yale University building is a physical structure on Yale’s campus designed to support the institution’s academic, residential, administrative, or cultural functions.
-
D.
Yale University library
Yale University Library is the system of libraries at Yale University that collectively house extensive academic, research, and special collections to support the university’s scholarly and educational missions.
-
E.
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.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:23 p.m.