Triple

T1166426
Position Surface form Disambiguated ID Type / Status
Subject RTCRtpReceiver E24809 entity
Predicate usedWith P4791 FINISHED
Object RTCPeerConnection E127263 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: RTCPeerConnection | Statement: [RTCRtpReceiver, usedWith, RTCPeerConnection]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RTCPeerConnection
Context triple: [RTCRtpReceiver, usedWith, RTCPeerConnection]
  • A. RTCPeerConnection chosen
    RTCPeerConnection is a WebRTC API interface that enables real-time audio, video, and data communication between web browsers or devices by managing the underlying peer-to-peer connection.
  • B. WebRTC
    WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
  • C. RTCIceCandidate
    RTCIceCandidate is a WebRTC interface representing a potential network route (ICE candidate) used during peer-to-peer connection negotiation.
  • 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. ORTC
    ORTC (Object Real-Time Communications) is a JavaScript API and architecture for enabling real-time audio, video, and data communications on the web, serving as an alternative and evolutionary step beyond the traditional WebRTC 1.0 model.
  • 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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bccc62a88190882d8801908015a4 completed March 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac668290008190a5e175c0a2e5feb0 completed March 7, 2026, 5:55 p.m.
Created at: March 1, 2026, 7:45 p.m.