Triple
T34542826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDF Vocabulary Description Language 1.0: RDF Schema |
E886847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RDF schema language |
C49393
|
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 schema language Context triple: [RDF Vocabulary Description Language 1.0: RDF Schema, instanceOf, RDF schema language]
-
A.
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.
-
B.
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.
-
C.
RDFa vocabulary
An RDFa vocabulary is a defined set of terms (URIs) used within RDFa-annotated markup to semantically describe resources and their relationships in web documents.
-
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.
RDF resource
chosen
An RDF resource is any identifiable entity (real or abstract) that can be uniquely referenced by a URI and described using RDF statements.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.