Triple
T21224593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1889 |
E523056
|
entity |
| Predicate | relatedSpecification |
P37
|
FINISHED |
| Object | RTCP |
—
|
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: RTCP | Statement: [RFC 1889, relatedSpecification, RTCP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RTCP Context triple: [RFC 1889, relatedSpecification, RTCP]
-
A.
RTP Profile for Audio and Video Conferences with Minimal Control
RTP Profile for Audio and Video Conferences with Minimal Control is an IETF standard (RFC 3551) that specifies payload formats and conventions for carrying audio and video over the Real-time Transport Protocol (RTP) in multimedia conferencing applications.
-
B.
RTSP
RTSP (Real Time Streaming Protocol) is a network control protocol designed for establishing and controlling media streaming sessions between endpoints over IP networks.
-
C.
RTCRtpSendParameters
RTCRtpSendParameters is a WebRTC configuration object that defines how media is sent over an RTP sender, including encodings, codecs, and header extensions.
-
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.
H.245
H.245 is an ITU-T control protocol used in multimedia communication systems to negotiate channel usage and capabilities between endpoints.
- 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: RTCP Target entity description: RTCP (Real-time Transport Control Protocol) is a companion protocol to RTP that provides quality-of-service feedback, synchronization, and control information for real-time audio and video streams over IP networks.
-
A.
RTP Profile for Audio and Video Conferences with Minimal Control
RTP Profile for Audio and Video Conferences with Minimal Control is an IETF standard (RFC 3551) that specifies payload formats and conventions for carrying audio and video over the Real-time Transport Protocol (RTP) in multimedia conferencing applications.
-
B.
RTSP
RTSP (Real Time Streaming Protocol) is a network control protocol designed for establishing and controlling media streaming sessions between endpoints over IP networks.
-
C.
RTCRtpSendParameters
RTCRtpSendParameters is a WebRTC configuration object that defines how media is sent over an RTP sender, including encodings, codecs, and header extensions.
-
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.
H.245
H.245 is an ITU-T control protocol used in multimedia communication systems to negotiate channel usage and capabilities between endpoints.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734aa82c4819086cef6364619b4e9 |
completed | April 21, 2026, 8:26 a.m. |
Created at: April 16, 2026, 3:44 p.m.