Triple
T22027895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediaStreamTrack |
E544011
|
entity |
| Predicate | createdBy |
P806
|
FINISHED |
| Object | RTCPeerConnection |
—
|
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: RTCPeerConnection | Statement: [MediaStreamTrack, createdBy, RTCPeerConnection]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RTCPeerConnection Context triple: [MediaStreamTrack, createdBy, 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.
RTCRtpTransceiver
RTCRtpTransceiver is a WebRTC API object that represents a bidirectional RTP media track pairing, managing both sending and receiving of a specific media stream over a peer connection.
-
E.
NAT and firewall traversal requirements for WebRTC
NAT and firewall traversal requirements for WebRTC are the standardized technical guidelines that ensure WebRTC media and data can reliably pass through network address translators and firewalls in real-world internet deployments.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cdf5c08190ac804664d6e56fe2 |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:24 p.m.