Triple
T7415164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORCID |
E171110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | persistent identifier provider |
C12581
|
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 provider Context triple: [ORCID, instanceOf, persistent identifier provider]
-
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.
identifier resolution system
chosen
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.
-
C.
index provider
An index provider is an entity or system that designs, calculates, maintains, and disseminates rules-based indices that track the performance of selected assets, markets, or strategies.
-
D.
UN/LOCODE identifier
A UN/LOCODE identifier is a standardized five-character code assigned by the United Nations to uniquely identify locations such as ports, cities, and transport hubs used in international trade and logistics.
-
E.
music release identifier
A music release identifier is a unique code or label assigned to a specific music release (such as an album, single, or EP) to distinguish it from all other releases across catalogs and distribution systems.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:11 p.m.