Triple
T26427816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDF 1.1 TriG – RDF Dataset Language |
E664414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RDF syntax |
C22201
|
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: RDF syntax Context triple: [RDF 1.1 TriG – RDF Dataset Language, instanceOf, RDF syntax]
-
A.
RDF serialization syntax
RDF serialization syntax is the set of concrete textual or binary formats (such as Turtle, RDF/XML, or JSON-LD) used to encode and exchange RDF graphs while preserving their underlying semantic structure.
-
B.
RDF 1.1 syntax
chosen
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.
-
C.
RDF mapping language
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.
ontology syntax
Ontology syntax is the formal set of rules and notations used to represent, structure, and interrelate concepts and relationships within an ontology in a machine- and human-readable way.
-
E.
RDF validation language
An RDF validation language is a formal specification used to define and check constraints on RDF data graphs, ensuring that RDF resources conform to expected shapes, structures, and data quality rules.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:47 p.m.