Triple
T1492186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPARQL |
E29603
|
entity |
| Predicate | version |
P3286
|
FINISHED |
| Object | SPARQL 1.1 |
E29603
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: SPARQL 1.1 | Statement: [SPARQL, version, SPARQL 1.1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SPARQL 1.1 Context triple: [SPARQL, version, SPARQL 1.1]
-
A.
SPARQL
chosen
SPARQL is a semantic query language and protocol used to retrieve and manipulate data stored in Resource Description Framework (RDF) format on the Semantic Web.
-
B.
RDF 1.1 Semantics
RDF 1.1 Semantics is a W3C specification that formally defines the meaning and logical foundations of RDF data, enabling consistent interpretation and reasoning across RDF graphs.
-
C.
RDF 1.1 Concepts and Abstract Syntax
RDF 1.1 Concepts and Abstract Syntax is a W3C specification that defines the core data model, terminology, and abstract syntax for the Resource Description Framework (RDF).
-
D.
RDF 1.1 XML Syntax
RDF 1.1 XML Syntax is a W3C specification that defines how RDF data is represented and serialized using XML.
-
E.
RDF 1.1 N-Quads
RDF 1.1 N-Quads is a W3C serialization format for RDF datasets that extends N-Triples by supporting named graphs through four-part statements.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c4f0c88190a97ba4910c1a5d85 |
completed | March 1, 2026, 11:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad58b487c08190bb2b1c259bd39db0 |
completed | March 8, 2026, 11:08 a.m. |
Created at: March 1, 2026, 8:12 p.m.