Triple
T10330538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C Membership Agreement |
E242860
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | W3C governance document |
C27885
|
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 governance document Context triple: [W3C Membership Agreement, instanceOf, W3C governance document]
-
A.
W3C Recommendation
A W3C Recommendation is a mature, stable web standard published by the World Wide Web Consortium that has undergone extensive review and is endorsed for widespread implementation on the Web.
-
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.
W3C specification
A W3C specification is an official, collaboratively developed technical standard published by the World Wide Web Consortium that defines interoperable protocols, formats, and best practices for the World Wide Web.
-
D.
W3C role
A W3C role is a semantic attribute value used in web content to define the purpose and behavior of an element, enhancing accessibility and interoperability across user agents and assistive technologies.
-
E.
W3C technical specification
A W3C technical specification is a formal, consensus-based document published by the World Wide Web Consortium that defines standards, protocols, and guidelines to ensure the interoperability and evolution of the World Wide Web.
- F. None of above. chosen
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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:52 a.m.