Triple
T24123106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebAssembly Community Group |
E597717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | W3C community group |
C22187
|
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: W3C community group Context triple: [WebAssembly Community Group, instanceOf, W3C community group]
-
A.
web standards community
chosen
A web standards community is a collaborative group of stakeholders—such as developers, browser vendors, and organizations—who work together to design, refine, and promote interoperable technical specifications that ensure the open, accessible, and consistent functioning of the web.
-
B.
W3C initiative
A W3C initiative is a coordinated effort or program led by the World Wide Web Consortium to develop, standardize, and promote open web technologies and best practices.
-
C.
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.
-
D.
W3C governance document
A W3C governance document defines the policies, processes, and organizational structures that guide decision-making, participation, and standardization activities within the World Wide Web Consortium.
-
E.
W3C participant
A W3C participant is an individual or organization that takes part in World Wide Web Consortium activities, such as working groups and community groups, to help develop and maintain open web standards.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:06 p.m.