Triple
T16747554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JaLC |
E406994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital object identifier registration agency |
C34935
|
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 object identifier registration agency Context triple: [JaLC, instanceOf, digital object identifier registration agency]
-
A.
persistent identifier service provider
chosen
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.
-
B.
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.
-
C.
bibliographic identifier
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.
-
D.
digital repository
A digital repository is a managed, long-term storage system that collects, preserves, and provides organized access to digital content and associated metadata.
-
E.
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.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.