Triple
T22197331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6062 |
E548581
|
entity |
| Predicate | protocolFamily |
P4615
|
FINISHED |
| Object | STUN/TURN |
—
|
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: STUN/TURN | Statement: [RFC 6062, protocolFamily, STUN/TURN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STUN/TURN Context triple: [RFC 6062, protocolFamily, STUN/TURN]
-
A.
STUN protocol
The STUN protocol (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port and determine the type of NAT or firewall they are behind to enable peer-to-peer connectivity.
-
B.
STUN
chosen
STUN (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port as seen by external servers, enabling communication across NAT and firewalls.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae8c74c819080c7f9e8383ecaa7 |
completed | April 28, 2026, 9:47 p.m. |
Created at: April 16, 2026, 8:35 p.m.