Triple
T7423223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON-LD |
E171299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Linked Data format |
C22200
|
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: Linked Data format Context triple: [JSON-LD, instanceOf, Linked Data format]
-
A.
bibliographic data format
A bibliographic data format is a structured specification for representing, organizing, and exchanging information about published and unpublished resources such as books, articles, and other media.
-
B.
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.
-
C.
Web ontology language
A web ontology language is a formal language designed for representing rich, machine-interpretable knowledge about concepts, relationships, and constraints on the web to enable automated reasoning and interoperability.
-
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.
open data index
An open data index is a systematic ranking or assessment framework that evaluates and compares the availability, accessibility, quality, and usability of open government or institutional data across different entities or jurisdictions.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:12 p.m.