Triple

T22814825
Position Surface form Disambiguated ID Type / Status
Subject IETF RFC 8826 E565070 entity
Predicate title P38 FINISHED
Object Security Considerations for WebRTC — 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: Security Considerations for WebRTC | Statement: [IETF RFC 8826, title, Security Considerations for WebRTC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Security Considerations for WebRTC
Context triple: [IETF RFC 8826, title, Security Considerations for WebRTC]
  • A. 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.
  • B. SRTP for secure media transport
    SRTP for secure media transport is a security protocol that encrypts and authenticates real-time audio and video streams, commonly used in VoIP and WebRTC communications.
  • C. WebRTC
    WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
  • D. WebRTC ICE
    WebRTC ICE (Interactive Connectivity Establishment) is a framework used in WebRTC to discover and select the best network path for peer-to-peer real-time communication across NATs and firewalls.
  • E. Media Path Key Agreement for Unicast Secure RTP
    Media Path Key Agreement for Unicast Secure RTP is a cryptographic protocol that establishes and manages encryption keys directly over the media path to secure one-to-one Real-time Transport Protocol (RTP) streams.
  • 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: Security Considerations for WebRTC
Target entity description: "Security Considerations for WebRTC" is an IETF RFC that analyzes the security threats, requirements, and recommended countermeasures for real-time communication systems built on WebRTC.
  • A. 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.
  • B. SRTP for secure media transport
    SRTP for secure media transport is a security protocol that encrypts and authenticates real-time audio and video streams, commonly used in VoIP and WebRTC communications.
  • C. WebRTC
    WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
  • D. WebRTC ICE
    WebRTC ICE (Interactive Connectivity Establishment) is a framework used in WebRTC to discover and select the best network path for peer-to-peer real-time communication across NATs and firewalls.
  • E. Media Path Key Agreement for Unicast Secure RTP
    Media Path Key Agreement for Unicast Secure RTP is a cryptographic protocol that establishes and manages encryption keys directly over the media path to secure one-to-one Real-time Transport Protocol (RTP) streams.
  • F. None of above. chosen

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_69e2458426188190b58b8ab4844fe420 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17dcb872881909a031d8560635fce completed April 29, 2026, 3:40 a.m.
Created at: April 17, 2026, 3:33 p.m.