Triple
T5768156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interactive Connectivity Establishment |
E127262
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | WebRTC ICE |
E24286
|
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 ICE | Statement: [Interactive Connectivity Establishment, relatedTo, WebRTC ICE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WebRTC ICE Context triple: [Interactive Connectivity Establishment, relatedTo, WebRTC ICE]
-
A.
WebRTC
WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
-
B.
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.
-
C.
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.
-
D.
RTCIceCandidate
chosen
RTCIceCandidate is a WebRTC interface representing a potential network route (ICE candidate) used during peer-to-peer connection negotiation.
-
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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029731adc8190888adc8178a08e90 |
completed | March 22, 2026, 5:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07e61127c8190833e279403af6605 |
completed | March 22, 2026, 11:42 p.m. |
Created at: March 22, 2026, 3:49 p.m.