Triple
T9931217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2104 |
E192651
|
entity |
| Predicate | standardizesUsageIn |
P1587
|
FINISHED |
| Object | IPsec |
E23863
|
NE FINISHED |
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: IPsec | Statement: [RFC 2104, standardizesUsageIn, IPsec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IPsec Context triple: [RFC 2104, standardizesUsageIn, 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.
IKEv1
IKEv1 is the original version of the Internet Key Exchange protocol used to establish secure, authenticated communication channels for IPsec VPNs.
-
D.
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.
-
E.
IKEv2
IKEv2 is a modern key management and security association protocol used to establish and maintain secure VPN connections in IPsec-based networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizesUsageIn Context triple: [RFC 2104, standardizesUsageIn, IPsec]
-
A.
scriptUsedForStandardization
Indicates that a particular writing system or script is employed as the standard reference form for normalizing or harmonizing text or data.
-
B.
standardizedIn
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
C.
usesStandard
chosen
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
D.
standardizedFor
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
-
E.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- F. None of above.
Provenance (4 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d228cab0fc81908ff5fad6916c1bab |
completed | April 5, 2026, 9:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.