Triple
T22814846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF RFC 8826 |
E565070
|
entity |
| Predicate | technologyScope |
P74633
|
FINISHED |
| Object | WebRTC |
—
|
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: WebRTC | Statement: [IETF RFC 8826, technologyScope, WebRTC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WebRTC Context triple: [IETF RFC 8826, technologyScope, 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.
WebRTC ICE
WebRTC ICE (Interactive Connectivity Establishment) is a framework used in WebRTC to discover and select the best network path for peer-to-peer real-time communication across NATs and firewalls.
-
C.
Twilio Video
Twilio Video is a cloud-based platform that enables developers to embed real-time video and audio communication into web and mobile applications using APIs and SDKs.
-
D.
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.
-
E.
Overview and Rationale for the WebRTC Framework
"Overview and Rationale for the WebRTC Framework" is an IETF RFC that explains the design goals, architectural principles, and key decisions underlying the WebRTC real-time communication framework.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcb872881909a031d8560635fce |
completed | April 29, 2026, 3:40 a.m. |
Created at: April 17, 2026, 3:33 p.m.