Triple
T25879340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OWL 2 Full |
E652003
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Semantic Web language |
C2887
|
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: Semantic Web language Context triple: [OWL 2 Full, instanceOf, Semantic Web language]
-
A.
Web ontology language
chosen
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.
-
B.
Knowledge representation language
A knowledge representation language is a formal system used to encode information about the world in a structured, machine-interpretable way so that computers can reason about it.
-
C.
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.
-
D.
linked data platform
A linked data platform is a system or framework that enables the publication, management, and consumption of interlinked RDF-based resources over the web using standard HTTP operations.
-
E.
Linked Data format
A Linked Data format is a structured way of representing and interconnecting data on the web using URIs, HTTP, and RDF-based standards so that resources can be uniquely identified, linked, and machine-interpretable.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:13 a.m.