Triple
T14547507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPIC Handle Service |
E341326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | persistent identifier service |
C34933
|
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: persistent identifier service Context triple: [EPIC Handle Service, instanceOf, persistent identifier service]
-
A.
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.
-
B.
bibliographic service suite
A bibliographic service suite is an integrated set of tools and services that support the creation, management, discovery, and sharing of bibliographic records and related metadata across information systems.
-
C.
bibliographic database provider
A bibliographic database provider is an organization or service that collects, curates, indexes, and delivers structured metadata about publications and scholarly works for search, discovery, and analysis.
-
D.
bibliographic authority data set
A bibliographic authority data set is a structured collection of standardized records that uniquely identify and describe entities (such as persons, organizations, works, and subjects) used to control and link names and headings in bibliographic and library catalogs.
-
E.
globally unique identifier
A globally unique identifier is a value, typically a long numeric or alphanumeric string, that is guaranteed (or practically guaranteed) to be unique across all systems, times, and contexts for reliably identifying an entity.
- F. None of above. chosen
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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.