Triple

T5768073
Position Surface form Disambiguated ID Type / Status
Subject RFC 5766 E127261 entity
Predicate extends P1244 FINISHED
Object Session Traversal Utilities for NAT E543994 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: Session Traversal Utilities for NAT | Statement: [RFC 5766, extends, Session Traversal Utilities for NAT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Session Traversal Utilities for NAT
Context triple: [RFC 5766, extends, Session Traversal Utilities for NAT]
  • 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. 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.
  • 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 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. RFC 3551
    RFC 3551 is an IETF standard that specifies the audio and video profile for the Real-time Transport Protocol (RTP), including default payload formats and parameter assignments for real-time multimedia communication.
  • 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_69c098062d2c8190a7ccddc1017e19e5 completed March 23, 2026, 1:31 a.m.
Created at: March 22, 2026, 3:49 p.m.