Triple
T22027530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RESERVATION-TOKEN |
E544004
|
entity |
| Predicate | belongsToRegistry |
P91198
|
FINISHED |
| Object | IANA STUN/TURN attributes registry |
—
|
NE NERFINISHED |
How this triple was built (3 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: IANA STUN/TURN attributes registry | Statement: [RESERVATION-TOKEN, belongsToRegistry, IANA STUN/TURN attributes registry]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IANA STUN/TURN attributes registry Context triple: [RESERVATION-TOKEN, belongsToRegistry, IANA STUN/TURN attributes registry]
-
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
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.
RFC 5389
RFC 5389 is the IETF specification that defines the Session Traversal Utilities for NAT (STUN) protocol used to discover public IP addresses and facilitate NAT traversal for real-time communications.
-
D.
RFC 5766
RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
-
E.
RFC 5245
RFC 5245 is the IETF specification that standardizes Interactive Connectivity Establishment (ICE), a framework for NAT traversal used to establish media and data connections in real-time communication protocols like SIP and WebRTC.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IANA STUN/TURN attributes registry Target entity description: The IANA STUN/TURN attributes registry is the official catalog maintained by the Internet Assigned Numbers Authority that defines and manages the standardized attribute codes used by STUN and TURN protocols for NAT traversal.
-
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
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.
RFC 5389
RFC 5389 is the IETF specification that defines the Session Traversal Utilities for NAT (STUN) protocol used to discover public IP addresses and facilitate NAT traversal for real-time communications.
-
D.
RFC 5766
RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
-
E.
RFC 5245
RFC 5245 is the IETF specification that standardizes Interactive Connectivity Establishment (ICE), a framework for NAT traversal used to establish media and data connections in real-time communication protocols like SIP and WebRTC.
- F. None of above. chosen
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_69f127cdf5c08190ac804664d6e56fe2 |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:24 p.m.