Triple

T575879
Position Surface form Disambiguated ID Type / Status
Subject Chromium E13759 entity
Predicate supportsStandard P1587 FINISHED
Object WebRTC 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 | Statement: [Chromium, supportsStandard, WebRTC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WebRTC
Context triple: [Chromium, supportsStandard, WebRTC]
  • 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. Zoom Video Communications
    Zoom Video Communications is a technology company best known for its widely used cloud-based video conferencing and online collaboration platform.
  • C. 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.
  • D. Webex
    Webex is Cisco’s cloud-based suite of video conferencing, online meeting, and team collaboration tools used by businesses and organizations worldwide.
  • 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_69a4933fa4d88190a7949cc83c08c5c1 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49b67395c8190a8046ff7debe9d1f completed March 1, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4ff4db0248190b2b3ca0290467313 completed March 2, 2026, 3:09 a.m.
Created at: March 1, 2026, 7:33 p.m.