Triple
T8390923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikidata Query Service |
E197940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SPARQL endpoint |
C24006
|
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: SPARQL endpoint Context triple: [Wikidata Query Service, instanceOf, SPARQL endpoint]
-
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.
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.
-
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.
Provider Backbone Bridges standard
The Provider Backbone Bridges standard defines a scalable Ethernet networking architecture that encapsulates customer traffic within provider-managed backbone networks to extend Layer 2 services across large metropolitan or wide-area domains.
-
E.
RDF 1.1 syntax
RDF 1.1 syntax defines the standardized concrete formats (such as Turtle, TriG, N-Triples, and N-Quads) and rules for serializing RDF graphs and datasets into machine- and human-readable text.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:03 p.m.