Triple

T1404945
Position Surface form Disambiguated ID Type / Status
Subject AES-GCM E31669 entity
Predicate usedInProtocol P3331 FINISHED
Object IPsec E23863 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: IPsec | Statement: [AES-GCM, usedInProtocol, IPsec]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IPsec
Context triple: [AES-GCM, usedInProtocol, IPsec]
  • A. IPsec chosen
    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.
  • B. 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.
  • C. IKEv2
    IKEv2 is a modern key management and security association protocol used to establish and maintain secure VPN connections in IPsec-based networks.
  • D. 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.
  • E. IEEE 802.1AE MACsec standard
    The IEEE 802.1AE MACsec standard is a network security protocol that provides data confidentiality, integrity, and origin authenticity for Ethernet traffic at the media access control (MAC) layer.
  • 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_69a49918e1f88190ba610f9dc8114578 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c3bb3a9c81909db2ad91defd87b6 completed March 1, 2026, 10:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69ace573b9288190ac91d8f6ea94fa20 completed March 8, 2026, 2:56 a.m.
Created at: March 1, 2026, 7:59 p.m.