Triple
T26938812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dLib.si |
E678456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national digital library |
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: national digital library Context triple: [dLib.si, instanceOf, national digital library]
-
A.
national library organization
A national library organization is a centralized institution responsible for collecting, preserving, and providing access to a country's published heritage and coordinating library services at the national level.
-
B.
national library building
A national library building is a large, often iconic public structure that houses and preserves a country's primary collection of published works and cultural heritage materials, providing spaces for research, study, and archival services.
-
C.
national electronic database
A national electronic database is a centralized digital system that securely stores, manages, and provides authorized access to large-scale data relevant to a country’s population, institutions, or services.
-
D.
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.
-
E.
national library of Estonia component
A national library of Estonia component represents any structural, functional, or informational part of the National Library of Estonia, such as its collections, services, departments, or digital systems, within a larger library management or architectural model.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:17 a.m.