Triple
T8852466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2821 |
E210669
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2197
RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
|
E774044
|
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 2197 | Statement: [RFC 2821, obsoletes, RFC 2197]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2197 Context triple: [RFC 2821, obsoletes, RFC 2197]
-
A.
RFC 2195
RFC 2195 is an Internet standard that specifies the CRAM-MD5 authentication mechanism for secure password-based login in protocols like IMAP and POP3.
-
B.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
-
E.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
- 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 2197 Triple: [RFC 2821, obsoletes, RFC 2197]
Generated description
RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2197 Target entity description: RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
-
A.
RFC 2195
RFC 2195 is an Internet standard that specifies the CRAM-MD5 authentication mechanism for secure password-based login in protocols like IMAP and POP3.
-
B.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
-
E.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c3c5548190926e374bbe592180 |
completed | April 1, 2026, 12:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfeb0dab088190b842b20f8a7bc7a0 |
completed | April 3, 2026, 4:30 p.m. |
| NEDg | Description generation | batch_69cfec4515308190be32a295619babdb |
completed | April 3, 2026, 4:35 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfecdc70048190813f715153ca0f0e |
completed | April 3, 2026, 4:37 p.m. |
Created at: March 30, 2026, 6:49 p.m.