Triple

T8816760
Position Surface form Disambiguated ID Type / Status
Subject ALPN E209795 entity
Predicate allowsNegotiationOf P34326 FINISHED
Object SPDY E39862 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: SPDY | Statement: [ALPN, allowsNegotiationOf, SPDY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SPDY
Context triple: [ALPN, allowsNegotiationOf, SPDY]
  • A. SPDY chosen
    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.
  • B. 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.
  • C. 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.
  • D. mod_spdy
    mod_spdy is an Apache HTTP Server module developed by Google to add support for the SPDY (and later HTTP/2) protocol, improving web performance through features like multiplexing and header compression.
  • E. 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.
  • 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_69ca8364e13081909c85fe80f44fe86f completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc600bd8a88190ad891a96201d796b completed April 1, 2026, midnight
NED1 Entity disambiguation (via context triple) batch_69cfa05742948190bcec72a080f6837a completed April 3, 2026, 11:11 a.m.
Created at: March 30, 2026, 6:46 p.m.