Triple
T22027400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5389 |
E544002
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Session Traversal Utilities for NAT (STUN) |
—
|
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: Session Traversal Utilities for NAT (STUN) | Statement: [RFC 5389, title, Session Traversal Utilities for NAT (STUN)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Session Traversal Utilities for NAT (STUN) Context triple: [RFC 5389, title, Session Traversal Utilities for NAT (STUN)]
-
A.
Session Traversal Utilities for NAT
chosen
Session Traversal Utilities for NAT (STUN) is a network protocol that enables devices behind Network Address Translators (NATs) to discover their public IP address and port mappings to facilitate real-time communication over the internet.
-
B.
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.
-
C.
STUN
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.
-
D.
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.
-
E.
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.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ccc2ec8190a94d69530d00c06c |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:24 p.m.