Triple
T17483467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Digital Repository |
E425720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital preservation system |
C2291
|
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: digital preservation system Context triple: [Stanford Digital Repository, instanceOf, digital preservation system]
-
A.
digital preservation organization
A digital preservation organization is an entity dedicated to ensuring the long-term accessibility, integrity, and usability of digital information through coordinated policies, technologies, and stewardship practices.
-
B.
digital repository
chosen
A digital repository is a managed, long-term storage system that collects, preserves, and provides organized access to digital content and associated metadata.
-
C.
digital librarian
A digital librarian is an information professional who curates, organizes, preserves, and facilitates access to digital collections and online resources using specialized tools, metadata standards, and information management practices.
-
D.
digital information management framework
A digital information management framework is a structured set of principles, processes, and tools for systematically capturing, organizing, securing, accessing, and governing digital data and content across its lifecycle.
-
E.
film preservation authority
A film preservation authority is an organization or governing body responsible for safeguarding, restoring, cataloging, and ensuring long-term access to motion picture materials and related audiovisual heritage.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:48 a.m.