Triple
T36432288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Borough Public Library central offices |
E897475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public library system headquarters |
C65975
|
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: public library system headquarters Context triple: [Queens Borough Public Library central offices, instanceOf, public library system headquarters]
-
A.
main library branch
The main library branch is the central facility in a library system that houses the largest collection, core services, and administrative offices, serving as the primary hub for patrons and branch libraries.
-
B.
public library system
A public library system is an organized network of libraries, resources, services, and policies that manages the acquisition, cataloging, circulation, and access to informational and cultural materials for a community.
-
C.
Chicago Public Library branch
A Chicago Public Library branch is a local public facility within the Chicago Public Library system that provides community access to books, digital resources, programs, and services.
-
D.
royal public library
A royal public library is a state-supported institution, historically patronized by a monarchy, that preserves and provides public access to a comprehensive collection of cultural, scholarly, and historical materials.
-
E.
Toronto Public Library branch
A Toronto Public Library branch is a local public facility within the Toronto Public Library system that provides community access to books, digital resources, programs, and services.
- F. None of above. chosen
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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.