Triple

T17417072
Position Surface form Disambiguated ID Type / Status
Subject VoIP E423515 entity
Predicate usesProtocol P203 FINISHED
Object Real-time Transport Protocol 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: Real-time Transport Protocol | Statement: [VoIP, usesProtocol, Real-time Transport Protocol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Real-time Transport Protocol
Context triple: [VoIP, usesProtocol, Real-time Transport Protocol]
  • A. Real-time Transport Control Protocol
    Real-time Transport Control Protocol (RTCP) is a companion protocol to RTP that provides out-of-band control, quality-of-service feedback, and synchronization for real-time audio and video streams over IP networks.
  • 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. RFC 3550
    RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
  • D. RTP Payload Format for Uncompressed Video
    RTP Payload Format for Uncompressed Video is an IETF specification that defines how raw, uncompressed video data is packetized and transported in real time over IP networks using the Real-time Transport Protocol (RTP).
  • E. RTSP
    RTSP (Real Time Streaming Protocol) is a network control protocol designed for establishing and controlling media streaming sessions between endpoints over IP networks.
  • 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: Real-time Transport Protocol
Target entity description: Real-time Transport Protocol is a network protocol designed for delivering audio and video data with low latency over IP networks, commonly used in real-time applications such as internet telephony and video conferencing.
  • A. Real-time Transport Control Protocol
    Real-time Transport Control Protocol (RTCP) is a companion protocol to RTP that provides out-of-band control, quality-of-service feedback, and synchronization for real-time audio and video streams over IP networks.
  • 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. RFC 3550 chosen
    RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
  • D. RTP Payload Format for Uncompressed Video
    RTP Payload Format for Uncompressed Video is an IETF specification that defines how raw, uncompressed video data is packetized and transported in real time over IP networks using the Real-time Transport Protocol (RTP).
  • E. RTSP
    RTSP (Real Time Streaming Protocol) is a network control protocol designed for establishing and controlling media streaming sessions between endpoints over IP networks.
  • 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e44233c7888190a4d2aa703b206851 completed April 19, 2026, 2:47 a.m.
Created at: April 10, 2026, 5:46 a.m.