Triple
T30016475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sy Syms School of Business |
E762609
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic division of Yeshiva 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 Yeshiva University Context triple: [Sy Syms School of Business, instanceOf, academic division of Yeshiva 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.
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.
-
C.
division of Rutgers University
A division of Rutgers University is a major organizational unit within the institution that groups related academic, administrative, or support functions under a unified leadership and mission.
-
D.
Lithuanian yeshiva
A Lithuanian yeshiva is a traditional Jewish institution of higher Talmudic learning, originating in 19th-century Lithuania, characterized by rigorous analytical study, intellectual discipline, and a focus on ethical and spiritual development.
-
E.
school of New York University
A school of New York University is an academic division within NYU that offers specialized degree programs, research opportunities, and faculty in a particular field of study under the broader university structure.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:46 p.m.