Triple
T18553274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonfly key exchange |
E453435
|
entity |
| Predicate | isDefinedIn |
P4464
|
FINISHED |
| Object | RFC 7664 |
—
|
NE NERFINISHED |
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: RFC 7664 | Statement: [Dragonfly key exchange, isDefinedIn, RFC 7664]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7664 Context triple: [Dragonfly key exchange, isDefinedIn, RFC 7664]
-
A.
RFC 6864
RFC 6864 is an Internet Engineering Task Force (IETF) standards-track document that revises and clarifies the semantics and usage of the IPv4 Identification field in IP packet headers.
-
B.
RFC 7674
RFC 7674 is an Internet standards document that specifies how to use DANE (DNS-Based Authentication of Named Entities) for securing email transport with TLS.
-
C.
RFC 5764
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
D.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
E.
RFC 7946
RFC 7946 is the IETF standard specification that defines the GeoJSON format for encoding geographic data structures in JSON.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 7664 Target entity description: RFC 7664 is an IETF standard that specifies the Dragonfly password-authenticated key exchange protocol used to establish secure cryptographic keys based on shared passwords.
-
A.
RFC 6864
RFC 6864 is an Internet Engineering Task Force (IETF) standards-track document that revises and clarifies the semantics and usage of the IPv4 Identification field in IP packet headers.
-
B.
RFC 7674
RFC 7674 is an Internet standards document that specifies how to use DANE (DNS-Based Authentication of Named Entities) for securing email transport with TLS.
-
C.
RFC 5764
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
D.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
E.
RFC 7946
RFC 7946 is the IETF standard specification that defines the GeoJSON format for encoding geographic data structures in JSON.
- F. None of above. chosen
Provenance (2 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538027b94819082a4c4af66e170d7 |
completed | April 19, 2026, 8:16 p.m. |
Created at: April 10, 2026, 11:38 a.m.