Triple

T1817438
Position Surface form Disambiguated ID Type / Status
Subject RFC 7232 E40465 entity
Predicate updatesProtocol P3696 FINISHED
Object HTTP/1.1 E8577 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/1.1 | Statement: [RFC 7232, updatesProtocol, HTTP/1.1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HTTP/1.1
Context triple: [RFC 7232, updatesProtocol, HTTP/1.1]
  • A. HTTP/1.1 chosen
    HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
  • B. HTTP
    HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
  • 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. 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.
  • E. TLS 1.1
    TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
  • 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_69a8864526c081908a3a4d74f689e2c5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa65f7b84081909005ce36ef1199db completed March 6, 2026, 5:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69adbf6019bc81909266b7f03b282f34 completed March 8, 2026, 6:26 p.m.
Created at: March 4, 2026, 7:32 p.m.