Triple
T1853310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7541 |
E41644
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object | HPACK |
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 | Statement: [RFC 7541, defines, HPACK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HPACK Context triple: [RFC 7541, defines, HPACK]
-
A.
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.
-
B.
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.
-
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.
QPACK
QPACK is a header compression mechanism designed for HTTP/3 over QUIC, improving upon HPACK to better handle multiplexed streams without head-of-line blocking.
-
E.
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.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb06b3f08819092b3fbdff83b3097 |
completed | March 7, 2026, 4:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adc9c9c6208190a2793994a7f927bd |
completed | March 8, 2026, 7:11 p.m. |
Created at: March 4, 2026, 7:33 p.m.