Triple

T2175110
Position Surface form Disambiguated ID Type / Status
Subject WebSockets Standard E48508 entity
Predicate defines P264 FINISHED
Object WebSocket protocol E48508 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: WebSocket protocol | Statement: [WebSockets Standard, defines, WebSocket protocol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WebSocket protocol
Context triple: [WebSockets Standard, defines, WebSocket protocol]
  • A. WebSockets Standard chosen
    The WebSockets Standard is a web technology specification that enables full-duplex, real-time communication between web browsers and servers over a single, long-lived connection.
  • B. WebRTC
    WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
  • C. QUIC
    QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
  • D. HTTP
    HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
  • E. 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.
  • 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_69a88aa3faa48190995b233af6525815 completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abbeccb2888190aa1fe1039e9dfbe2 completed March 7, 2026, 5:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae653b6ae48190ab5c7e6bf2dcfa6f completed March 9, 2026, 6:14 a.m.
Created at: March 4, 2026, 7:45 p.m.