Triple

T8816758
Position Surface form Disambiguated ID Type / Status
Subject ALPN E209795 entity
Predicate allowsNegotiationOf P34326 FINISHED
Object HTTP/2 E6319 NE FINISHED

How this triple was built (3 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 | Statement: [ALPN, allowsNegotiationOf, HTTP/2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HTTP/2
Context triple: [ALPN, allowsNegotiationOf, HTTP/2]
  • 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. 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.
  • C. 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.
  • D. 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.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsNegotiationOf
Context triple: [ALPN, allowsNegotiationOf, HTTP/2]
  • A. negotiatedPursuantTo
    Indicates that a negotiation occurred in accordance with, or as required by, a specific agreement, rule, provision, or legal/contractual framework.
  • B. negotiationAssociatedWith
    Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
  • C. allows
    Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
  • D. negotiatedVia
    Indicates that an agreement, deal, or arrangement was reached through the use of a specific intermediary, channel, or method of negotiation.
  • E. negotiationMechanism chosen
    Indicates a process or method through which parties communicate and bargain to reach a mutually acceptable agreement.
  • F. None of above.

Provenance (4 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.
PD Predicate disambiguation batch_69cc5c21e64c81908490e3b0875dc0d6 completed March 31, 2026, 11:43 p.m.
Created at: March 30, 2026, 6:46 p.m.