Triple
T8697125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7540 |
E206428
|
entity |
| Predicate | relatedSpecification |
P37
|
FINISHED |
| Object | HPACK: Header Compression for HTTP/2 |
E40363
|
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: HPACK: Header Compression for HTTP/2 | Statement: [RFC 7540, relatedSpecification, HPACK: Header Compression for HTTP/2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HPACK: Header Compression for HTTP/2 Context triple: [RFC 7540, relatedSpecification, HPACK: Header Compression for HTTP/2]
-
A.
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.
-
B.
HPACK
chosen
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
-
C.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
D.
Version-Independent Properties of QUIC
"Version-Independent Properties of QUIC" is an IETF RFC that defines the core invariants and fundamental design characteristics of the QUIC transport protocol that remain consistent across all protocol versions.
-
E.
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.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582b04688190a439135b08e20451 |
completed | March 31, 2026, 11:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cef4060410819086f928bda95e0273 |
completed | April 2, 2026, 10:56 p.m. |
Created at: March 30, 2026, 6:34 p.m.