Triple
T22027184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF BEHAVE working group |
E543996
|
entity |
| Predicate | produced |
P490
|
FINISHED |
| Object | RFC 6888 title Common Requirements for Carrier-Grade NATs (CGNs) |
—
|
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: RFC 6888 title Common Requirements for Carrier-Grade NATs (CGNs) | Statement: [IETF BEHAVE working group, produced, RFC 6888 title Common Requirements for Carrier-Grade NATs (CGNs)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6888 title Common Requirements for Carrier-Grade NATs (CGNs) Context triple: [IETF BEHAVE working group, produced, RFC 6888 title Common Requirements for Carrier-Grade NATs (CGNs)]
-
A.
RFC 4288
RFC 4288 is an Internet standards document that defines the procedures and guidelines for registering and managing media (MIME) types with IANA.
-
B.
RFC 6528
RFC 6528 is an Internet Engineering Task Force (IETF) standard that specifies improved methods for generating TCP initial sequence numbers to enhance security against spoofing and related attacks.
-
C.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
-
D.
RFC 6698
RFC 6698 is the Internet standard that specifies the DNS-Based Authentication of Named Entities (DANE) protocol, which uses DNSSEC to associate TLS certificates with domain names.
-
E.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that specifies the use of SHA-2 data integrity verification algorithms within the Secure Shell (SSH) protocol.
- 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: RFC 6888 title Common Requirements for Carrier-Grade NATs (CGNs) Target entity description: RFC 6888 is an IETF standards document that specifies functional and operational requirements for carrier-grade NAT (CGN) devices used by service providers to share IPv4 addresses at large scale.
-
A.
RFC 6888
chosen
RFC 6888 is an Internet Engineering Task Force (IETF) standard that specifies requirements and behavior for Carrier-Grade NAT (CGN) devices used by service providers to share IPv4 addresses among multiple customers.
-
B.
Session Traversal Utilities for NAT
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.
-
C.
RFC 4288
RFC 4288 is an Internet standards document that defines the procedures and guidelines for registering and managing media (MIME) types with IANA.
-
D.
RFC 6528
RFC 6528 is an Internet Engineering Task Force (IETF) standard that specifies improved methods for generating TCP initial sequence numbers to enhance security against spoofing and related attacks.
-
E.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
- F. None of above.
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.