Triple

T1817403
Position Surface form Disambiguated ID Type / Status
Subject RFC 7232 E40465 entity
Predicate title P38 FINISHED
Object Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests E40465 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: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests | Statement: [RFC 7232, title, Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
Context triple: [RFC 7232, title, Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests]
  • A. RFC 7235
    RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
  • B. RFC 7232 chosen
    RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
  • C. RFC 7234
    RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
  • D. RFC 7230
    RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
  • E. RFC 7231
    RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
  • 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.