Triple

T1812675
Position Surface form Disambiguated ID Type / Status
Subject HPACK E40363 entity
Predicate workingGroup P9939 FINISHED
Object IETF HTTPbis Working Group E49793 NE FINISHED

How this triple was built (2 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 HTTPbis Working Group | Statement: [HPACK, workingGroup, IETF HTTPbis Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IETF HTTPbis Working Group
Context triple: [HPACK, workingGroup, IETF HTTPbis Working Group]
  • A. 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.
  • B. HTTP Working Group chosen
    The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
  • C. IETF ICE Working Group
    The IETF ICE Working Group is a standards body team within the Internet Engineering Task Force responsible for developing and maintaining the Interactive Connectivity Establishment (ICE) protocols used for NAT traversal in real-time communications.
  • D. IETF working groups
    IETF working groups are collaborative teams of experts within the Internet Engineering Task Force that develop and standardize technical specifications and protocols for the Internet.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69a88643a3388190a612f2ebe1fb29e7 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa65c775408190b4f5912786720e28 completed March 6, 2026, 5:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69adb5e5142c8190bc90da38b02e95e2 completed March 8, 2026, 5:46 p.m.
Created at: March 4, 2026, 7:32 p.m.