Triple

T22232974
Position Surface form Disambiguated ID Type / Status
Subject RFC 6189 E549514 entity
Predicate relatedTo P37 FINISHED
Object Secure RTP NE NERFINISHED

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: Secure RTP | Statement: [RFC 6189, relatedTo, Secure RTP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Secure RTP
Context triple: [RFC 6189, relatedTo, Secure RTP]
  • A. SRTP for secure media transport chosen
    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.
  • B. DTLS-SRTP
    DTLS-SRTP is a security protocol framework that uses Datagram Transport Layer Security to negotiate keys and provide encryption and authentication for Secure Real-time Transport Protocol media streams, commonly used in VoIP and WebRTC.
  • C. ZRTP
    ZRTP is a cryptographic key-agreement protocol designed to enable end-to-end encryption for real-time voice and video communications over RTP-based systems.
  • D. Secure Digital
    Secure Digital is a widely used non-volatile memory card format for portable devices such as cameras, smartphones, and tablets.
  • E. H.235 security framework
    The H.235 security framework is an ITU-T standard that defines authentication, integrity, and encryption mechanisms to secure H.323-based multimedia communication over packet networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e11e4102b881909cf47d3768e25c19 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12bf4e0348190b755a9ac0bc96cdd completed April 28, 2026, 9:51 p.m.
Created at: April 16, 2026, 8:38 p.m.