Triple
T7444663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five College Libraries Depository |
E171845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-density library storage facility |
C9582
|
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: high-density library storage facility Context triple: [Five College Libraries Depository, instanceOf, high-density library storage facility]
-
A.
library storage facility
chosen
A library storage facility is a specialized space designed to house, preserve, and organize less frequently used library materials in a secure, climate-controlled environment while keeping them retrievable on demand.
-
B.
secure storage facility
A secure storage facility is a highly protected, access-controlled environment designed to safely store valuable, sensitive, or hazardous items against theft, damage, and unauthorized access.
-
C.
industrial storage facility
An industrial storage facility is a large, purpose-built structure designed to securely house, organize, and manage bulk materials, goods, or equipment used in manufacturing, logistics, or distribution operations.
-
D.
high-level radioactive waste storage facility
A high-level radioactive waste storage facility is a secure, engineered site designed to safely contain and isolate highly radioactive materials from the environment and human populations for extended periods of time.
-
E.
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.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:14 p.m.