Triple

T5959101
Position Surface form Disambiguated ID Type / Status
Subject RFC 3711 E132589 entity
Predicate appliesTo P1129 FINISHED
Object RTCP E127658 NE FINISHED

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: RTCP | Statement: [RFC 3711, appliesTo, RTCP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RTCP
Context triple: [RFC 3711, appliesTo, RTCP]
  • A. Real-time Transport Control Protocol chosen
    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. RFC 3550
    RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
  • C. RTCRtpEncodingParameters
    RTCRtpEncodingParameters is a WebRTC configuration object that defines how a particular RTP stream is encoded, including settings like bitrate, scalability, and redundancy for real-time audio or video transmission.
  • D. RTCRtpReceiver
    RTCRtpReceiver is a WebRTC API interface that represents the receiving end of an RTP media stream, providing access to incoming audio or video tracks and related reception statistics.
  • E. SCTP
    SCTP (Stream Control Transmission Protocol) is a transport-layer network protocol designed to provide reliable, message-oriented communication with features like multi-streaming and multi-homing, often used for signaling and real-time data transmission.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c0086c2364819091e9fe2f58fa2517 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c039fbf49881909d97b4abb3c5286d completed March 22, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e3e3736c8190b445156f0c1bdf1f completed March 23, 2026, 6:55 a.m.
Created at: March 22, 2026, 4:02 p.m.