Triple
T22586066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford University departments |
E564796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic division collection |
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 collection Context triple: [Oxford University departments, instanceOf, academic division collection]
-
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.
academic library department
An academic library department is an organizational unit within a college or university library that manages specific functions—such as reference services, collections, instruction, or technical processing—to support the institution’s teaching, learning, and research missions.
-
C.
academic district
An academic district is a designated area within a city or region where educational institutions and related facilities are concentrated, fostering learning, research, and scholarly activities.
-
D.
campus facility collection
A campus facility collection is an organized set of physical spaces, buildings, and infrastructure on an educational campus that together support academic, residential, recreational, and administrative activities.
-
E.
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.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 2:46 p.m.