Triple
T21802410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2795
RFC 2795 is an April Fools' joke RFC titled "The Infinite Monkey Protocol Suite (IMPS)," humorously describing a fictional protocol based on the infinite monkey theorem.
|
E1503625
|
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 2795 | Statement: [RFC 4632, obsoletes, RFC 2795]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2795 Context triple: [RFC 4632, obsoletes, RFC 2795]
-
A.
RFC 2793
RFC 2793 is an older Internet Engineering Task Force (IETF) specification that defined an early standard related to IP networking, later superseded by RFC 4632.
-
B.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
C.
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.
-
D.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
E.
RFC 4395
RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
- 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 2795 Triple: [RFC 4632, obsoletes, RFC 2795]
Generated description
RFC 2795 is an April Fools' joke RFC titled "The Infinite Monkey Protocol Suite (IMPS)," humorously describing a fictional protocol based on the infinite monkey theorem.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2795 Target entity description: RFC 2795 is an April Fools' joke RFC titled "The Infinite Monkey Protocol Suite (IMPS)," humorously describing a fictional protocol based on the infinite monkey theorem.
-
A.
RFC 2793
RFC 2793 is an older Internet Engineering Task Force (IETF) specification that defined an early standard related to IP networking, later superseded by RFC 4632.
-
B.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
C.
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.
-
D.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
E.
RFC 4395
RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0a45d8a5688190a469c1a1c8a8d6ec |
completed | May 17, 2026, 10:48 p.m. |
| NEDg | Description generation | batch_6a0a46d528c08190b17fb11c73e22270 |
completed | May 17, 2026, 10:53 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0a472d34d08190a25ba431e24e8316 |
completed | May 17, 2026, 10:54 p.m. |
Created at: April 16, 2026, 6:53 p.m.