Triple

T270968
Position Surface form Disambiguated ID Type / Status
Subject HTTP/3 E5630 entity
Predicate workingGroup P9939 FINISHED
Object IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
E35277 NE FINISHED

How this triple was built (5 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: IETF QUIC Working Group | Statement: [HTTP/3, workingGroup, IETF QUIC Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IETF QUIC Working Group
Context triple: [HTTP/3, workingGroup, IETF QUIC Working Group]
  • A. QUIC
    QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
  • B. IETF RTCWEB Working Group
    The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
  • C. HTTP/3
    HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
  • D. Internet Engineering Steering Group
    The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
  • E. IEEE 802.1 Working Group
    The IEEE 802.1 Working Group is a standards body within the IEEE 802 LAN/MAN Standards Committee responsible for developing and maintaining networking standards for bridging, network management, and time-sensitive networking.
  • 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: IETF QUIC Working Group
Triple: [HTTP/3, workingGroup, IETF QUIC Working Group]
Generated description
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: IETF QUIC Working Group
Target entity description: The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
  • A. QUIC
    QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
  • B. IETF RTCWEB Working Group
    The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
  • C. HTTP/3
    HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
  • D. Internet Engineering Steering Group
    The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
  • E. IEEE 802.1 Working Group
    The IEEE 802.1 Working Group is a standards body within the IEEE 802 LAN/MAN Standards Committee responsible for developing and maintaining networking standards for bridging, network management, and time-sensitive networking.
  • F. None of above. chosen
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: workingGroup
Context triple: [HTTP/3, workingGroup, IETF QUIC Working Group]
  • A. worksWith
    Indicates that two entities collaborate or perform tasks together in a shared work-related context.
  • B. team
    Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
  • C. fieldOfWork
    Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
  • D. workedUnder
    Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of another entity.
  • E. committeeFunction
    Indicates that a committee performs, is responsible for, or is associated with a particular function or role.
  • F. None of above. chosen

Provenance (7 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_69a25853594c8190b05ec3a586ec88bf completed Feb. 28, 2026, 2:52 a.m.
NER Named-entity recognition batch_69a25e69a9248190b9e7959b43223baa completed Feb. 28, 2026, 3:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69a38f51aeac81908c6d398e650dc315 completed March 1, 2026, 12:58 a.m.
NEDg Description generation batch_69a38fbfac808190b2b551dcbfe6faff completed March 1, 2026, 1 a.m.
NED2 Entity disambiguation (via description) batch_69a3903779e88190a00c44a522e82022 completed March 1, 2026, 1:02 a.m.
PD Predicate disambiguation batch_69a25b721180819080d43c43fcbccf87 completed Feb. 28, 2026, 3:05 a.m.
PDg Predicate description generation batch_69a25e68f0408190bfc851c32d6eebf3 completed Feb. 28, 2026, 3:18 a.m.
Created at: Feb. 28, 2026, 2:57 a.m.