Triple

T21264730
Position Surface form Disambiguated ID Type / Status
Subject RFC 3948 E524096 entity
Predicate title P38 FINISHED
Object UDP Encapsulation of IPsec ESP Packets — 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: UDP Encapsulation of IPsec ESP Packets | Statement: [RFC 3948, title, UDP Encapsulation of IPsec ESP Packets]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: UDP Encapsulation of IPsec ESP Packets
Context triple: [RFC 3948, title, UDP Encapsulation of IPsec ESP Packets]
  • A. Encapsulating Security Payload
    Encapsulating Security Payload (ESP) is a core IPsec protocol that provides confidentiality, integrity, and optional authentication for IP packets through encryption and encapsulation.
  • B. IPsec
    IPsec is a suite of protocols that provides secure, encrypted communication over IP networks by authenticating and protecting the integrity and confidentiality of data packets.
  • C. IPsec over TCP
    IPsec over TCP is a method of encapsulating IPsec traffic within TCP packets to traverse restrictive firewalls and NAT devices that block traditional IPsec protocols.
  • D. Internet Protocol fragmentation and reassembly
    Internet Protocol fragmentation and reassembly is the process by which large IP packets are split into smaller fragments for transmission across networks with limited maximum transmission units and then reassembled back into the original packet at the destination.
  • E. TCP/IP header compression
    TCP/IP header compression is a technique that significantly reduces the size of TCP/IP packet headers to improve performance over low-bandwidth or high-latency network links.
  • 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: UDP Encapsulation of IPsec ESP Packets
Target entity description: UDP Encapsulation of IPsec ESP Packets is an IETF specification that defines how to transport IPsec ESP traffic over UDP, primarily to enable IPsec operation through Network Address Translators (NATs) and firewalls.
  • A. Encapsulating Security Payload
    Encapsulating Security Payload (ESP) is a core IPsec protocol that provides confidentiality, integrity, and optional authentication for IP packets through encryption and encapsulation.
  • B. IPsec
    IPsec is a suite of protocols that provides secure, encrypted communication over IP networks by authenticating and protecting the integrity and confidentiality of data packets.
  • C. IPsec over TCP
    IPsec over TCP is a method of encapsulating IPsec traffic within TCP packets to traverse restrictive firewalls and NAT devices that block traditional IPsec protocols.
  • D. Internet Protocol fragmentation and reassembly
    Internet Protocol fragmentation and reassembly is the process by which large IP packets are split into smaller fragments for transmission across networks with limited maximum transmission units and then reassembled back into the original packet at the destination.
  • E. TCP/IP header compression
    TCP/IP header compression is a technique that significantly reduces the size of TCP/IP packet headers to improve performance over low-bandwidth or high-latency network links.
  • 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_69e0b5156d7881909bd4f83676590715 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e735ea74e0819099d724de95996c90 completed April 21, 2026, 8:31 a.m.
Created at: April 16, 2026, 4 p.m.