Triple

T17519800
Position Surface form Disambiguated ID Type / Status
Subject websockets E426654 entity
Predicate supportsStandard P1587 FINISHED
Object RFC 6455 NE NERFINISHED

How this triple was built (3 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 6455 | Statement: [websockets, supportsStandard, RFC 6455]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 6455
Context triple: [websockets, supportsStandard, RFC 6455]
  • A. WebSockets Standard
    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. RFC 8445
    RFC 8445 is the IETF specification that modernizes and clarifies the Interactive Connectivity Establishment (ICE) protocol for NAT traversal in real-time communications.
  • C. 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.
  • D. RFC 8554
    RFC 8554 is an Internet standards document that specifies the Edwards-curve Digital Signature Algorithm (EdDSA), defining how to use modern elliptic-curve signatures in Internet protocols.
  • E. RFC 6347
    RFC 6347 is the Internet Engineering Task Force (IETF) standard that specifies Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over datagram-based transports such as UDP.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 6455
Target entity description: RFC 6455 is the IETF specification that defines the WebSocket protocol, enabling full-duplex, real-time communication between web clients and servers over a single TCP connection.
  • 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. RFC 8445
    RFC 8445 is the IETF specification that modernizes and clarifies the Interactive Connectivity Establishment (ICE) protocol for NAT traversal in real-time communications.
  • C. 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.
  • D. RFC 8554
    RFC 8554 is an Internet standards document that specifies the Edwards-curve Digital Signature Algorithm (EdDSA), defining how to use modern elliptic-curve signatures in Internet protocols.
  • E. RFC 6347
    RFC 6347 is the Internet Engineering Task Force (IETF) standard that specifies Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over datagram-based transports such as UDP.
  • F. None of above.

Provenance (2 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_69d889de677081909b22d2657b1f0292 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e452d18c1c81908bb843bbddb44ca1 completed April 19, 2026, 3:58 a.m.
Created at: April 10, 2026, 5:49 a.m.