Triple
T26427583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PROV |
E664409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provenance data model |
C18774
|
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: provenance data model Context triple: [PROV, instanceOf, provenance data model]
-
A.
bibliographic data model
A bibliographic data model is a structured framework that defines how information about published and unpublished resources (such as books, articles, and digital media) is represented, organized, and related for purposes of description, discovery, and management.
-
B.
Ontology-Based Data Access system
An Ontology-Based Data Access system is a framework that uses a formal ontology to provide a unified, semantic view over heterogeneous data sources, enabling users to query data at a conceptual level without needing to know the underlying schemas or storage details.
-
C.
data model
chosen
A data model is an abstract, structured representation of data and its relationships, designed to organize, define, and constrain how information is stored, accessed, and manipulated within a system.
-
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.
linked data platform
A linked data platform is a system or framework that enables the publication, management, and consumption of interlinked RDF-based resources over the web using standard HTTP operations.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:46 p.m.