Triple

T1160098
Position Surface form Disambiguated ID Type / Status
Subject Node.js E24471 entity
Predicate supports P516 FINISHED
Object WebSockets 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: WebSockets | Statement: [Node.js, supports, WebSockets]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WebSockets
Context triple: [Node.js, supports, WebSockets]
  • 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. RTCPeerConnection
    RTCPeerConnection is a WebRTC API interface that enables real-time audio, video, and data communication between web browsers or devices by managing the underlying peer-to-peer connection.
  • D. WebGL
    WebGL is a JavaScript API that enables hardware-accelerated 2D and 3D graphics rendering within web browsers without the need for plugins.
  • E. WebAssembly JavaScript Interface
    The WebAssembly JavaScript Interface is the standard API that defines how JavaScript code interacts with and controls WebAssembly modules within web browsers and other host environments.
  • 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_69a494060e148190abb42f971242c197 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcaf3a9081908bad2eba74dffbc1 completed March 1, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac5ebbf80881909010e1e1e59212d4 completed March 7, 2026, 5:22 p.m.
Created at: March 1, 2026, 7:45 p.m.