Triple
T9931590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3447 |
E192659
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 8017 |
E37200
|
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: RFC 8017 | Statement: [RFC 3447, obsoletedBy, RFC 8017]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8017 Context triple: [RFC 3447, obsoletedBy, RFC 8017]
-
A.
RFC 8017
chosen
RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
-
B.
RFC 8016
RFC 8016 is an Internet Engineering Task Force (IETF) specification that updates the TURN protocol to improve how it relays traffic for clients behind Network Address Translators (NATs).
-
C.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
-
D.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
E.
RFC 3447
RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
- 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_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. |
Created at: March 30, 2026, 8:43 p.m.