Triple

T394773
Position Surface form Disambiguated ID Type / Status
Subject RFC 9114 E8958 entity
Predicate workingGroup P9939 FINISHED
Object HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
 E49793 NE FINISHED

How this triple was built (4 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: HTTP Working Group | Statement: [RFC 9114, workingGroup, HTTP Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: HTTP Working Group
Context triple: [RFC 9114, workingGroup, HTTP Working Group]
  • A. Web Hypertext Application Technology Working Group
    The Web Hypertext Application Technology Working Group (WHATWG) is a community of browser vendors, web developers, and other stakeholders that collaboratively develops and maintains key web standards, including the HTML Living Standard.
  • B. 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.
  • C. 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.
  • D. W3C Interest Group
    A W3C Interest Group is a community within the World Wide Web Consortium that brings together stakeholders to discuss and explore specific web-related topics without necessarily producing formal standards.
  • E. W3C Technical Architecture Group
    The W3C Technical Architecture Group is a specialized body within the World Wide Web Consortium that steers the evolution of web architecture and ensures the consistency and integrity of web standards.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: HTTP Working Group
Triple: [RFC 9114, workingGroup, HTTP Working Group]
Generated description
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: HTTP Working Group
Target entity description: The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
  • A. Web Hypertext Application Technology Working Group
    The Web Hypertext Application Technology Working Group (WHATWG) is a community of browser vendors, web developers, and other stakeholders that collaboratively develops and maintains key web standards, including the HTML Living Standard.
  • B. 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.
  • C. 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.
  • D. W3C Interest Group
    A W3C Interest Group is a community within the World Wide Web Consortium that brings together stakeholders to discuss and explore specific web-related topics without necessarily producing formal standards.
  • E. W3C Technical Architecture Group
    The W3C Technical Architecture Group is a specialized body within the World Wide Web Consortium that steers the evolution of web architecture and ensures the consistency and integrity of web standards.
  • F. None of above. chosen

Provenance (5 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_69a2e7f55c60819097aff65ea2ca2832 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec77a8a08190b6f96373aa8c1346 completed Feb. 28, 2026, 1:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69a405fa43448190b3e78d83e791b105 completed March 1, 2026, 9:25 a.m.
NEDg Description generation batch_69a4070f76308190bd898dcdb27f3277 completed March 1, 2026, 9:29 a.m.
NED2 Entity disambiguation (via description) batch_69a40794523081908839f90446beba83 completed March 1, 2026, 9:32 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.