Triple

T22027919
Position Surface form Disambiguated ID Type / Status
Subject RTCDataChannel E544012 entity
Predicate definedIn P775 FINISHED
Object WebRTC 1.0 specification 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: WebRTC 1.0 specification | Statement: [RTCDataChannel, definedIn, WebRTC 1.0 specification]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WebRTC 1.0 specification
Context triple: [RTCDataChannel, definedIn, WebRTC 1.0 specification]
  • A. WebRTC
    WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
  • B. IETF RTCWEB Working Group
    The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
  • C. Media Capture and Streams specification
    The Media Capture and Streams specification is a W3C standard that defines how web applications can access and control audio and video streams from devices like cameras and microphones, enabling features such as getUserMedia in browsers.
  • D. 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.
  • E. NAT and firewall traversal requirements for WebRTC
    NAT and firewall traversal requirements for WebRTC are the standardized technical guidelines that ensure WebRTC media and data can reliably pass through network address translators and firewalls in real-world internet deployments.
  • 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: WebRTC 1.0 specification
Target entity description: The WebRTC 1.0 specification is a W3C standard that defines APIs enabling real-time audio, video, and data communication directly between web browsers and other devices without requiring plugins.
  • A. WebRTC chosen
    WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
  • B. IETF RTCWEB Working Group
    The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
  • C. Media Capture and Streams specification
    The Media Capture and Streams specification is a W3C standard that defines how web applications can access and control audio and video streams from devices like cameras and microphones, enabling features such as getUserMedia in browsers.
  • D. 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.
  • E. NAT and firewall traversal requirements for WebRTC
    NAT and firewall traversal requirements for WebRTC are the standardized technical guidelines that ensure WebRTC media and data can reliably pass through network address translators and firewalls in real-world internet deployments.
  • 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_69e11e2e8ea4819084210fe06d3a1b8d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127cdf5c08190ac804664d6e56fe2 completed April 28, 2026, 9:34 p.m.
Created at: April 16, 2026, 8:24 p.m.