Triple

T8697082
Position Surface form Disambiguated ID Type / Status
Subject RFC 7540 E206428 entity
Predicate title P38 FINISHED
Object Hypertext Transfer Protocol Version 2 (HTTP/2) E6319 NE FINISHED

Named-entity recognition

Before disambiguation, gpt-5-mini classified whether the object phrase is a named entity — the step behind the object's NE type shown above.

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: Hypertext Transfer Protocol Version 2 (HTTP/2) | Statement: [RFC 7540, title, Hypertext Transfer Protocol Version 2 (HTTP/2)]

Disambiguation candidates (1 decision)

The exact options the model was shown at each disambiguation step, with the option it chose highlighted — the evidence behind this triple's disambiguated ids.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hypertext Transfer Protocol Version 2 (HTTP/2)
Context triple: [RFC 7540, title, Hypertext Transfer Protocol Version 2 (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. 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)

Stage Batch ID Job type Status
creating batch_69ca83555b6c8190abe930dd397e863b elicitation completed
NER batch_69cc582b04688190a439135b08e20451 ner completed
NED1 batch_69cef4060410819086f928bda95e0273 ned_source_triple completed
Created at: March 30, 2026, 6:34 p.m.