Triple
T10532237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. Barnes |
E248472
|
entity |
| Predicate | authorOf |
P4244
|
FINISHED |
| Object |
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that specifies the use of SHA-2 data integrity verification algorithms within the Secure Shell (SSH) protocol.
|
E869766
|
NE FINISHED |
How this triple was built (4 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 6668 | Statement: [R. Barnes, authorOf, RFC 6668]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6668 Context triple: [R. Barnes, authorOf, RFC 6668]
-
A.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
-
B.
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.
-
C.
RFC 6698
RFC 6698 is the Internet standard that specifies the DNS-Based Authentication of Named Entities (DANE) protocol, which uses DNSSEC to associate TLS certificates with domain names.
-
D.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 6668 Triple: [R. Barnes, authorOf, RFC 6668]
Generated description
RFC 6668 is an Internet Engineering Task Force (IETF) standard that specifies the use of SHA-2 data integrity verification algorithms within the Secure Shell (SSH) protocol.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6668 Target entity description: RFC 6668 is an Internet Engineering Task Force (IETF) standard that specifies the use of SHA-2 data integrity verification algorithms within the Secure Shell (SSH) protocol.
-
A.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
-
B.
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.
-
C.
RFC 6698
RFC 6698 is the Internet standard that specifies the DNS-Based Authentication of Named Entities (DANE) protocol, which uses DNSSEC to associate TLS certificates with domain names.
-
D.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
E.
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.
- F. None of above. chosen
Provenance (5 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a17f23081909f3372e160e21670 |
completed | April 7, 2026, 1:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d90e471e9c8190b134249073b289bd |
completed | April 10, 2026, 2:50 p.m. |
| NEDg | Description generation | batch_69d9107f488481908845aef0fdf6d60d |
completed | April 10, 2026, 3 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d911790010819093fc50952502fd59 |
completed | April 10, 2026, 3:04 p.m. |
Created at: April 6, 2026, 12:30 p.m.