Triple

T1096703
Position Surface form Disambiguated ID Type / Status
Subject RTCIceCandidate E24286 entity
Predicate partOf P40 FINISHED
Object WebRTC API 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 API | Statement: [RTCIceCandidate, partOf, WebRTC API]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WebRTC API
Context triple: [RTCIceCandidate, partOf, WebRTC API]
  • 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. Audio Video Bridging
    Audio Video Bridging (AVB) is a set of IEEE standards that enable time-synchronized, low-latency audio and video streaming over Ethernet networks.
  • D. 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.
  • E. IETF RTCWEB Working Group
    The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
  • 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_69a4940542308190ac2a0b1f730b7cfc completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b99ffb3481908cd168b6c58e1c6d completed March 1, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac59a058b88190beb883bf35377316 completed March 7, 2026, 5 p.m.
Created at: March 1, 2026, 7:42 p.m.