Triple
T10208120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP Alternative Services specification |
E242257
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object | Alt-Svc HTTP header field |
E242257
|
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: Alt-Svc HTTP header field | Statement: [HTTP Alternative Services specification, defines, Alt-Svc HTTP header field]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alt-Svc HTTP header field Context triple: [HTTP Alternative Services specification, defines, Alt-Svc HTTP header field]
-
A.
HTTP Alternative Services specification
chosen
The HTTP Alternative Services specification is an IETF standard that defines a mechanism for HTTP servers to advertise alternative network endpoints or protocols that clients can use to access the same resources more efficiently or reliably.
-
B.
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.
-
C.
ALPN (Application-Layer Protocol Negotiation)
ALPN (Application-Layer Protocol Negotiation) is a TLS extension that allows clients and servers to agree on which application-layer protocol (such as HTTP/2 or SPDY) to use over a secure connection during the TLS handshake.
-
D.
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.
-
E.
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.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d395f8e2b881909c51f8210f09cd4f |
completed | April 6, 2026, 11:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d652c13d748190908d1869c60e84c3 |
completed | April 8, 2026, 1:06 p.m. |
Created at: April 6, 2026, 10:57 a.m.