Triple
T7928166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8314 |
E184119
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
|
E700355
|
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 2595 | Statement: [RFC 8314, obsoletes, RFC 2595]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2595 Context triple: [RFC 8314, obsoletes, RFC 2595]
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
RFC 2574
RFC 2574 is an earlier IETF specification that defined the User-based Security Model (USM) for securing SNMPv3 communications before being superseded by RFC 3414.
-
D.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
-
E.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
- 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 2595 Triple: [RFC 8314, obsoletes, RFC 2595]
Generated description
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2595 Target entity description: RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
RFC 2574
RFC 2574 is an earlier IETF specification that defined the User-based Security Model (USM) for securing SNMPv3 communications before being superseded by RFC 3414.
-
D.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
-
E.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5bfd08e88190bc6b2d77a148ae57 |
completed | March 31, 2026, 5:30 a.m. |
| NEDg | Description generation | batch_69cb7633c5a0819089deb6e89d9acb8e |
completed | March 31, 2026, 7:22 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69cbb84dc86c8190893d67ce07c51aa0 |
completed | March 31, 2026, 12:04 p.m. |
Created at: March 30, 2026, 5:07 p.m.