Triple
T5479264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAT-T |
E123430
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | IKEv1 |
E522215
|
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: IKEv1 | Statement: [NAT-T, relatedTo, IKEv1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IKEv1 Context triple: [NAT-T, relatedTo, IKEv1]
-
A.
IKEv1
chosen
IKEv1 is the original version of the Internet Key Exchange protocol used to establish secure, authenticated communication channels for IPsec VPNs.
-
B.
IKEv2
IKEv2 is a modern key management and security association protocol used to establish and maintain secure VPN connections in IPsec-based networks.
-
C.
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.
-
D.
IEEE 802.11i
IEEE 802.11i is a Wi‑Fi security standard that enhances wireless network protection by defining robust encryption and authentication mechanisms, including WPA2.
-
E.
RFC 4301
RFC 4301 is an IETF standard that defines the Security Architecture for IP, including the core framework and mechanisms for IPsec-based network security.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf6c7a61848190970a4e34696791eb |
completed | March 22, 2026, 4:13 a.m. |
Created at: March 20, 2026, 2:09 p.m.