Triple
T24131072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stokes Library |
E597953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Princeton University library branch |
C34607
|
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: Princeton University library branch Context triple: [Stokes Library, instanceOf, Princeton University library branch]
-
A.
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.
-
B.
Stanford University library
Stanford University Library is the academic library system of Stanford University, providing extensive print and digital collections, research support, and study spaces to students, faculty, and scholars.
-
C.
Princeton University facility
chosen
A Princeton University facility is any physical building, structure, or space owned, leased, or operated by Princeton University that supports its academic, research, residential, administrative, or extracurricular functions.
-
D.
Rutgers University building
A Rutgers University building is a physical structure located on one of Rutgers’ campuses that houses academic, administrative, research, residential, or student-life functions associated with the university.
-
E.
Dartmouth College building
A Dartmouth College building is any physical structure owned, operated, or primarily used by Dartmouth College for academic, administrative, residential, athletic, or support purposes on or affiliated with its campus.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:25 p.m.