Triple
T10156746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transfer-Encoding header field |
E233793
|
entity |
| Predicate | usedWith |
P4791
|
FINISHED |
| Object | HTTP persistent connections |
E1064
|
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 persistent connections | Statement: [Transfer-Encoding header field, usedWith, HTTP persistent connections]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP persistent connections Context triple: [Transfer-Encoding header field, usedWith, HTTP persistent connections]
-
A.
Persistent Connections API
Persistent Connections API is a low-level ASP.NET SignalR programming model that lets developers manage real-time, bidirectional communication over a single long-lived connection with fine-grained control over messaging behavior.
-
B.
HTTP Datagrams
HTTP Datagrams are a mechanism for sending unreliable, connection-associated data alongside HTTP requests and responses, enabling low-latency, datagram-style communication over HTTP.
-
C.
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.
-
D.
HTTP
chosen
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
E.
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.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec3c47dc81909679903e6024eb49 |
completed | April 2, 2026, 4:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e65b9d4c8190b1f520ed08256372 |
completed | April 5, 2026, 10:46 p.m. |
Created at: March 30, 2026, 9:09 p.m.