Triple
T2263004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7539 |
E50080
|
entity |
| Predicate | useCase |
P98
|
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: [RFC 7539, useCase, IPsec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IPsec Context triple: [RFC 7539, useCase, 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.
MPLS
MPLS (Multiprotocol Label Switching) is a high-performance routing technique that directs data through a network using short path labels instead of long network addresses, enabling efficient traffic engineering and VPN services.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc18be8308190abc4a59d37dfd93a |
completed | March 7, 2026, 6:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71cfd3b08190988474aa0fa985fe |
completed | March 9, 2026, 7:08 a.m. |
Created at: March 4, 2026, 7:48 p.m.