Triple
T471922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 9113 |
E8576
|
entity |
| Predicate | definesConcept |
P773
|
FINISHED |
| Object | HTTP/2 server push |
E6319
|
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: HTTP/2 server push | Statement: [RFC 9113, definesConcept, HTTP/2 server push]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP/2 server push Context triple: [RFC 9113, definesConcept, HTTP/2 server push]
-
A.
HTTP/2
chosen
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.
-
B.
SPDY
SPDY is an experimental, now-deprecated web protocol developed by Google to speed up and secure HTTP traffic, which heavily influenced the design of HTTP/2.
-
C.
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.
-
D.
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.
-
E.
HTTP Caching
HTTP Caching is the standardized mechanism in the HTTP protocol that defines how responses can be stored and reused to improve web performance, reduce latency, and decrease network load.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eff0ca408190958405aec2ec6f53 |
completed | Feb. 28, 2026, 1:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a462fbc760819092a3065fbb0ef589 |
completed | March 1, 2026, 4:02 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.