Triple

T8816689
Position Surface form Disambiguated ID Type / Status
Subject Jetty E209793 entity
Predicate supports P516 FINISHED
Object WebSocket 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 | Statement: [Jetty, supports, WebSocket]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WebSocket
Context triple: [Jetty, supports, WebSocket]
  • 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. websockets (Python websockets library)
    websockets is a Python library for building asynchronous WebSocket clients and servers, providing a simple, asyncio-based API for real-time, bidirectional communication over the WebSocket protocol.
  • C. Socket.io
    Socket.io is a JavaScript library that enables real-time, bidirectional, event-based communication between web clients and servers over WebSockets and fallback transports.
  • D. WebRTC
    WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
  • E. LWS
    LWS is the IATA airport code for the regional airport serving Lewiston, Idaho.
  • 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_69ca8364e13081909c85fe80f44fe86f completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc600bd8a88190ad891a96201d796b completed April 1, 2026, midnight
NED1 Entity disambiguation (via context triple) batch_69cf6fc1579c8190ade0f780183aa1dc completed April 3, 2026, 7:44 a.m.
Created at: March 30, 2026, 6:46 p.m.