Triple
T8300481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikibase |
E194337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | linked data platform |
C23873
|
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 platform Context triple: [Wikibase, instanceOf, linked data platform]
-
A.
Linked Data format
A Linked Data format is a structured way of representing and interconnecting data on the web using URIs, HTTP, and RDF-based standards so that resources can be uniquely identified, linked, and machine-interpretable.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
open data platform
An open data platform is a system that collects, manages, and publishes structured datasets with standardized formats and open access policies, enabling users to discover, download, and reuse data freely.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:53 p.m.