Triple

T8672318
Position Surface form Disambiguated ID Type / Status
Subject HTTP authentication framework E205826 entity
Predicate appliesToProtocol P1129 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: [HTTP authentication framework, appliesToProtocol, HTTP/1.1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HTTP/1.1
Context triple: [HTTP authentication framework, appliesToProtocol, 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. RFC 2616
    RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
  • 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_69ca83529a9c8190b5c075b4f14636ed completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc491a34d08190b0795079d192a03d completed March 31, 2026, 10:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69cecd3a3c5c8190940a61e7e7b3e887 completed April 2, 2026, 8:10 p.m.
Created at: March 30, 2026, 6:31 p.m.