Triple

T53992
Position Surface form Disambiguated ID Type / Status
Subject HTTP E1064 entity
Predicate definedIn P775 FINISHED
Object RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
E8576 NE FINISHED

How this triple was built (4 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: RFC 9113 | Statement: [HTTP, definedIn, RFC 9113]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 9113
Context triple: [HTTP, definedIn, RFC 9113]
  • A. RFC 9111
    RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
  • B. RFC 9112
    RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
  • C. RFCs
    RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
  • D. RFC 8446
    RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
  • E. RFC 4252
    RFC 4252 is an Internet standard that specifies the authentication protocol used by Secure Shell (SSH) for secure remote login and other network services.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 9113
Triple: [HTTP, definedIn, RFC 9113]
Generated description
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 9113
Target entity description: RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
  • A. RFC 9111
    RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
  • B. RFC 9112
    RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
  • C. RFCs
    RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
  • D. RFC 8446
    RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
  • E. RFC 4252
    RFC 4252 is an Internet standard that specifies the authentication protocol used by Secure Shell (SSH) for secure remote login and other network services.
  • F. None of above. chosen

Provenance (5 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_69a248adc5b48190aa8db9fb092fb28a completed Feb. 28, 2026, 1:45 a.m.
NER Named-entity recognition batch_69a24ec4d84c81908d85a1e941dbcd19 completed Feb. 28, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69a2623ecff48190bc390f8d418b97ec completed Feb. 28, 2026, 3:34 a.m.
NEDg Description generation batch_69a262b29fc88190a1562e4dbe10d438 completed Feb. 28, 2026, 3:36 a.m.
NED2 Entity disambiguation (via description) batch_69a2634b24d08190b4869d235516c2ab completed Feb. 28, 2026, 3:38 a.m.
Created at: Feb. 28, 2026, 1:50 a.m.