Triple
T21802407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2792
RFC 2792 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
|
E1520528
|
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 2792 | Statement: [RFC 4632, obsoletes, RFC 2792]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2792 Context triple: [RFC 4632, obsoletes, RFC 2792]
-
A.
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.
-
B.
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.
-
C.
RFC 3492
RFC 3492 is the Internet standard document that defines Punycode, an encoding method used to represent Unicode characters in domain names using only ASCII characters.
-
D.
RFC 2774
RFC 2774 is an Internet Engineering Task Force (IETF) document that originally specified an HTTP Extension Framework, later superseded by RFC 4632.
-
E.
RFC 2072
RFC 2072 is an older Internet Engineering Task Force (IETF) document that was later superseded by RFC 4632, which refined and updated its technical specifications.
- 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 2792 Triple: [RFC 4632, obsoletes, RFC 2792]
Generated description
RFC 2792 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2792 Target entity description: RFC 2792 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
-
A.
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.
-
B.
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.
-
C.
RFC 3492
RFC 3492 is the Internet standard document that defines Punycode, an encoding method used to represent Unicode characters in domain names using only ASCII characters.
-
D.
RFC 2774
RFC 2774 is an Internet Engineering Task Force (IETF) document that originally specified an HTTP Extension Framework, later superseded by RFC 4632.
-
E.
RFC 2072
RFC 2072 is an older Internet Engineering Task Force (IETF) document that was later superseded by RFC 4632, which refined and updated its technical specifications.
- 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_6a0a8f0650448190897c27ae4de1dbdf |
completed | May 18, 2026, 4:01 a.m. |
| NEDg | Description generation | batch_6a0a935f48748190a217e72780635460 |
completed | May 18, 2026, 4:19 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0a93e870888190b7ce0bfd1b74bcef |
completed | May 18, 2026, 4:22 a.m. |
Created at: April 16, 2026, 6:53 p.m.