Triple

T7934820
Position Surface form Disambiguated ID Type / Status
Subject IKE E184261 entity
Predicate usedFor P98 FINISHED
Object IPsec VPNs 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 VPNs | Statement: [IKE, usedFor, IPsec VPNs]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IPsec VPNs
Context triple: [IKE, usedFor, IPsec VPNs]
  • 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. 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.
  • 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. OpenVPN
    OpenVPN is an open-source virtual private network (VPN) solution that enables secure, encrypted connections over the internet for remote access and site-to-site networking.
  • E. IKEv1
    IKEv1 is the original version of the Internet Key Exchange protocol used to establish secure, authenticated communication channels for IPsec VPNs.
  • 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_69ca8290c21c8190906a5ca6fe2b03c4 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3aec394081909a9569c02ac372af completed March 31, 2026, 3:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5c0791e48190af18299c22f6a804 completed March 31, 2026, 5:30 a.m.
Created at: March 30, 2026, 5:08 p.m.