Triple

T1166611

Position	Surface form	Disambiguated ID	Type / Status
Subject	IETF RTCWEB Working Group	`E24812`	entity
Predicate	defines	`P264`	FINISHED
Object	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.	`E134383`	NE FINISHED

How this triple was built (4 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: NAT and firewall traversal requirements for WebRTC | Statement: [IETF RTCWEB Working Group, defines, NAT and firewall traversal requirements for WebRTC]

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: NAT and firewall traversal requirements for WebRTC
Context triple: [IETF RTCWEB Working Group, defines, NAT and firewall traversal requirements for WebRTC]

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. 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. Traversal Using Relays around NAT
Traversal Using Relays around NAT (TURN) is a network protocol that enables devices behind firewalls or NATs to communicate by relaying their traffic through an intermediate server.
D. NAT-T
NAT-T (NAT Traversal) is an IPsec extension that enables VPN traffic to pass through Network Address Translation devices by encapsulating IPsec packets in UDP.
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. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NEDg Description generation gpt-5.1

Instruction

Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"

Input

Entity: NAT and firewall traversal requirements for WebRTC
Triple: [IETF RTCWEB Working Group, defines, NAT and firewall traversal requirements for WebRTC]

Generated description

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.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: NAT and firewall traversal requirements for WebRTC
Target entity description: 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.

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. 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. Traversal Using Relays around NAT
Traversal Using Relays around NAT (TURN) is a network protocol that enables devices behind firewalls or NATs to communicate by relaying their traffic through an intermediate server.
D. NAT-T
NAT-T (NAT Traversal) is an IPsec extension that enables VPN traffic to pass through Network Address Translation devices by encapsulating IPsec packets in UDP.
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. chosen

Provenance (5 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_69a494082a7c819095004f423f294a64`	completed	March 1, 2026, 7:31 p.m.
NER	Named-entity recognition	`batch_69a4bccd75048190b8ce88237c1a748b`	completed	March 1, 2026, 10:25 p.m.
NED1	Entity disambiguation (via context triple)	`batch_69ac668290008190a5e175c0a2e5feb0`	completed	March 7, 2026, 5:55 p.m.
NEDg	Description generation	`batch_69ac6aaa84fc81908130543b14938e41`	completed	March 7, 2026, 6:12 p.m.
NED2	Entity disambiguation (via description)	`batch_69ac6b24987c819080e00b49df8f6edb`	completed	March 7, 2026, 6:15 p.m.

Created at: March 1, 2026, 7:45 p.m.