Triple
T14423674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android WebView |
E357642
|
entity |
| Predicate | supports |
P516
|
FINISHED |
| Object | WebRTC (on newer versions) |
E3760
|
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: WebRTC (on newer versions) | Statement: [Android WebView, supports, WebRTC (on newer versions)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WebRTC (on newer versions) Context triple: [Android WebView, supports, WebRTC (on newer versions)]
-
A.
WebRTC
chosen
WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
-
B.
RTCPeerConnection
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.
-
C.
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.
-
D.
Jitsi
Jitsi is an open-source, cross-platform suite of real-time voice, video, and chat communication tools focused on secure, encrypted conferencing.
-
E.
Media Capture and Streams specification
The Media Capture and Streams specification is a W3C standard that defines how web applications can access and control audio and video streams from devices like cameras and microphones, enabling features such as getUserMedia in browsers.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91123f848190ba3fb18a76c2d24c |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bcd2a908190ad7d5ebf11b41551 |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.