Triple
T2187941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP Working Group |
E49793
|
entity |
| Predicate | responsibleFor |
P636
|
FINISHED |
| Object |
HTTP/3 QPACK header compression specification
The HTTP/3 QPACK header compression specification defines the mechanism for efficiently compressing HTTP header fields over QUIC while avoiding head-of-line blocking.
|
E246372
|
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/3 QPACK header compression specification | Statement: [HTTP Working Group, responsibleFor, HTTP/3 QPACK header compression specification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP/3 QPACK header compression specification Context triple: [HTTP Working Group, responsibleFor, HTTP/3 QPACK header compression specification]
-
A.
HPACK
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
-
B.
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.
-
C.
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.
-
D.
RFC 7540
RFC 7540 is the Internet Engineering Task Force (IETF) standard that defines HTTP/2, the major revision of the Hypertext Transfer Protocol designed to improve web performance and efficiency.
-
E.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
- 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/3 QPACK header compression specification Triple: [HTTP Working Group, responsibleFor, HTTP/3 QPACK header compression specification]
Generated description
The HTTP/3 QPACK header compression specification defines the mechanism for efficiently compressing HTTP header fields over QUIC while avoiding head-of-line blocking.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: HTTP/3 QPACK header compression specification Target entity description: The HTTP/3 QPACK header compression specification defines the mechanism for efficiently compressing HTTP header fields over QUIC while avoiding head-of-line blocking.
-
A.
HPACK
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
-
B.
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.
-
C.
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.
-
D.
RFC 7540
RFC 7540 is the Internet Engineering Task Force (IETF) standard that defines HTTP/2, the major revision of the Hypertext Transfer Protocol designed to improve web performance and efficiency.
-
E.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf130ef081908adb4a22f056be5b |
completed | March 7, 2026, 6 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae654016a88190a242d43491f0726c |
completed | March 9, 2026, 6:14 a.m. |
| NEDg | Description generation | batch_69ae6851d44c8190b9df8416d1b7be8d |
completed | March 9, 2026, 6:27 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae68ac638c8190adf98ca6144ea6a6 |
completed | March 9, 2026, 6:29 a.m. |
Created at: March 4, 2026, 7:45 p.m.