Triple

T1812602
Position Surface form Disambiguated ID Type / Status
Subject RFC 7231 E40362 entity
Predicate title P38 FINISHED
Object Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content E42395 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): Semantics and Content | Statement: [RFC 7231, title, Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Context triple: [RFC 7231, title, Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content]
  • A. Architecture of the World Wide Web, Volume One
    Architecture of the World Wide Web, Volume One is a W3C-authored technical document that defines the foundational principles and design of the Web’s architecture.
  • B. RFC 7230 chosen
    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.
  • C. RFC 2068
    RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
  • D. HTTP/1.1
    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.
  • E. RFC 7541
    RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
  • 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_69a88643a3388190a612f2ebe1fb29e7 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa65c775408190b4f5912786720e28 completed March 6, 2026, 5:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69adb5e5142c8190bc90da38b02e95e2 completed March 8, 2026, 5:46 p.m.
Created at: March 4, 2026, 7:32 p.m.