Triple
T20106886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISIL DE-12 |
E490200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | library identifier |
C1033
|
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: library identifier Context triple: [ISIL DE-12, instanceOf, library identifier]
-
A.
bibliographic identifier
chosen
A bibliographic identifier is a standardized code or string that uniquely distinguishes a specific published or unpublished bibliographic resource within catalogs, databases, or information systems.
-
B.
library cataloging standard
A library cataloging standard is a formal set of rules and guidelines that ensures consistent description, organization, and access to library materials across collections and systems.
-
C.
persistent identifier service
A persistent identifier service is a system that creates, manages, and resolves stable, long-lasting identifiers that reliably reference digital or physical resources over time, regardless of changes to their location or metadata.
-
D.
persistent identifier service provider
A persistent identifier service provider is an organization or system that creates, manages, and resolves long-lasting, globally unique identifiers to ensure stable access to digital or physical resources over time.
-
E.
library cataloging tool
A library cataloging tool is a system that helps librarians and users organize, classify, and retrieve library materials efficiently through standardized metadata and search functions.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:28 p.m.