Triple
T27584904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Query View Transformation |
E699668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | model transformation language standard |
C11252
|
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: model transformation language standard Context triple: [Query View Transformation, instanceOf, model transformation language standard]
-
A.
markup language standard
A markup language standard is a formally defined set of rules and syntax for structuring, annotating, and representing data or documents in a consistent, interoperable format.
-
B.
data transformation language
chosen
A data transformation language is a specialized programming or query language designed to define, manipulate, and convert data from one structure or format into another.
-
C.
language standard annex
A language standard annex is a supplementary section of a programming language specification that defines optional, extended, or locale-specific features beyond the core standard.
-
D.
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.
-
E.
syntax specification language
A syntax specification language is a formal notation used to define the grammatical structure and valid constructs of a programming or data language.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:04 p.m.