Triple
T17023216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mcom |
E412996
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | OAI-PMH repository identifier |
C38668
|
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: OAI-PMH repository identifier Context triple: [mcom, instanceOf, OAI-PMH repository identifier]
-
A.
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.
-
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.
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.
-
E.
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.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:33 a.m.