Triple
T33437144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoSPARQL |
E856262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SPARQL extension |
C50509
|
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 extension Context triple: [GeoSPARQL, instanceOf, SPARQL extension]
-
A.
SPARQL query engine
A SPARQL query engine is a software component that parses, optimizes, and executes SPARQL queries over RDF data sources to retrieve and manipulate semantic web data.
-
B.
SPARQL endpoint
A SPARQL endpoint is a web-accessible service that accepts SPARQL queries and returns results from an underlying RDF dataset.
-
C.
RDF mapping language
chosen
An RDF mapping language is a formal language used to define how data from various sources is transformed and expressed as RDF triples, enabling semantic integration and interoperability across heterogeneous systems.
-
D.
SDP extension mechanism
An SDP extension mechanism is a structured method for adding new attributes, media types, or capabilities to the Session Description Protocol while preserving backward compatibility and interoperability between endpoints.
-
E.
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.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.