Triple
T14547685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persistent Uniform Resource Locator |
E341330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | persistent identifier |
C24330
|
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 Context triple: [Persistent Uniform Resource Locator, instanceOf, persistent identifier]
-
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.
globally unique identifier
chosen
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.
-
C.
cryptography identifier
A cryptography identifier is a unique label or reference used to distinguish and manage specific cryptographic elements such as keys, algorithms, certificates, or protocols within a security system.
-
D.
identifier resolution system
An identifier resolution system is a mechanism that maps unique identifiers to their corresponding resources or entities, enabling consistent lookup, retrieval, and management across distributed or heterogeneous environments.
-
E.
music identifier standard
A music identifier standard is a formalized system for uniquely labeling and cataloging musical works, recordings, and related entities to enable consistent identification, tracking, and interoperability across platforms and databases.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.