Triple
T10449263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/3 QPACK header compression specification |
E246372
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HTTP/3 component |
C18013
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: HTTP/3 component Context triple: [HTTP/3 QPACK header compression specification, instanceOf, HTTP/3 component]
-
A.
network protocol component
chosen
A network protocol component is a modular element within a communication system that implements specific protocol functions—such as message formatting, routing, error handling, or session management—to enable reliable data exchange between networked entities.
-
B.
HTTP extension
An HTTP extension is an addition to the core HTTP protocol that introduces new headers, methods, or behaviors to support extra functionality while remaining compatible with existing HTTP infrastructure.
-
C.
TLS extension
A TLS extension is an optional, standardized addition to the TLS protocol that allows clients and servers to negotiate extra capabilities or parameters (such as supported protocols, server names, or security features) during the handshake.
-
D.
host-to-host protocol
A host-to-host protocol is a communication protocol that provides end-to-end data transfer and control services directly between two networked computers, abstracting the underlying network details.
-
E.
library network
A library network is an interconnected system of libraries that share resources, services, and information to provide broader and more efficient access to materials for their communities.
- F. None of above.
Provenance (1 batch)
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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:16 p.m.