Triple
T26427365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semantic Web Best Practices and Deployment Working Group |
E664404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Semantic Web working group |
C27881
|
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 working group Context triple: [Semantic Web Best Practices and Deployment Working Group, instanceOf, Semantic Web working group]
-
A.
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.
-
B.
W3C Technical Architecture Group finding
A W3C Technical Architecture Group finding is an authoritative document that articulates the TAG’s consensus guidance on architectural principles and best practices for the World Wide Web.
-
C.
Ontology-Based Data Access system
An Ontology-Based Data Access system is a framework that uses a formal ontology to provide a unified, semantic view over heterogeneous data sources, enabling users to query data at a conceptual level without needing to know the underlying schemas or storage details.
-
D.
World Wide Web Consortium resource
chosen
A World Wide Web Consortium resource is any document, specification, guideline, tool, or service produced or maintained by the W3C to develop and promote open web standards and best practices.
-
E.
World Wide Web conference
The World Wide Web conference is an annual international academic and industry event focused on the advancement, research, and standardization of web technologies and applications.
- 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:46 p.m.