Triple

T22041246
Position Surface form Disambiguated ID Type / Status
Subject Web Performance API E544641 entity
Predicate standardizedBy P1371 FINISHED
Object W3C Web Performance Working Group NE NERFINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: W3C Web Performance Working Group | Statement: [Web Performance API, standardizedBy, W3C Web Performance Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: W3C Web Performance Working Group
Context triple: [Web Performance API, standardizedBy, W3C Web Performance Working Group]
  • A. Web Applications Working Group
    The Web Applications Working Group is a W3C standards body responsible for developing and maintaining core web platform APIs and specifications that enable rich, interactive web applications.
  • B. W3C Working Group
    A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
  • C. W3C Team
    The W3C Team is the group of staff and technical experts responsible for leading, coordinating, and supporting the World Wide Web Consortium’s standards development and related activities.
  • D. W3C CSS Working Group
    The W3C CSS Working Group is the World Wide Web Consortium team responsible for designing and standardizing Cascading Style Sheets (CSS) for the web.
  • E. W3C Coordination Group
    The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: W3C Web Performance Working Group
Target entity description: The W3C Web Performance Working Group is a World Wide Web Consortium group that develops and maintains standards and APIs to measure, analyze, and improve web application performance across browsers.
  • A. Web Applications Working Group
    The Web Applications Working Group is a W3C standards body responsible for developing and maintaining core web platform APIs and specifications that enable rich, interactive web applications.
  • B. W3C Working Group
    A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
  • C. W3C Team
    The W3C Team is the group of staff and technical experts responsible for leading, coordinating, and supporting the World Wide Web Consortium’s standards development and related activities.
  • D. W3C CSS Working Group
    The W3C CSS Working Group is the World Wide Web Consortium team responsible for designing and standardizing Cascading Style Sheets (CSS) for the web.
  • E. W3C Coordination Group
    The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
  • F. None of above. chosen

Provenance (2 batches)

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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12828fc788190a22c0e9c2372656b completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:25 p.m.