Triple
T17377107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Vet |
E422467
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic division of the University of Pennsylvania |
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 the University of Pennsylvania Context triple: [Penn Vet, instanceOf, academic division of the University of Pennsylvania]
-
A.
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.
-
B.
academic division of the University of Virginia
An academic division of the University of Virginia is a formally organized unit within the university, such as a school or college, responsible for specific disciplines, degree programs, faculty, and academic administration.
-
C.
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.
-
D.
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.
-
E.
University of Pittsburgh school
A University of Pittsburgh school is an academic division within the University of Pittsburgh that offers specialized programs, conducts research, and provides instruction in a particular field or set of disciplines.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.