Triple
T21191110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2406 |
E522212
|
entity |
| Predicate | specifiesProtocolFor |
P12564
|
FINISHED |
| Object | confidentiality in IPsec |
—
|
LITERAL 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: confidentiality in IPsec | Statement: [RFC 2406, specifiesProtocolFor, confidentiality in IPsec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesProtocolFor Context triple: [RFC 2406, specifiesProtocolFor, confidentiality in IPsec]
-
A.
specifiesProtocol
chosen
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
B.
specifiesProtocolExtensionFor
Indicates that one protocol extension defines or constrains the behavior, capabilities, or usage of another protocol.
-
C.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
D.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
-
E.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
- F. None of above.
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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.