Triple
T21802413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2798
RFC 2798 is an Internet standards document that originally defined the LDAP schema for representing people in organizational directories before being superseded by later specifications.
|
E1536716
|
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 2798 | Statement: [RFC 4632, obsoletes, RFC 2798]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2798 Context triple: [RFC 4632, obsoletes, RFC 2798]
-
A.
RFC 2797
RFC 2797 is an Internet standards document that originally specified the Certificate Management Messages over CMS (CMC) protocol for managing X.509 digital certificates.
-
B.
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.
-
C.
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.
-
D.
RFC 2796
RFC 2796 is an Internet Engineering Task Force (IETF) document that specified an early version of the Multiprotocol Extensions for BGP-4 used to support multiple network layer protocols in inter-domain routing.
-
E.
RFC 2792
RFC 2792 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
- 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 2798 Triple: [RFC 4632, obsoletes, RFC 2798]
Generated description
RFC 2798 is an Internet standards document that originally defined the LDAP schema for representing people in organizational directories before being superseded by later specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2798 Target entity description: RFC 2798 is an Internet standards document that originally defined the LDAP schema for representing people in organizational directories before being superseded by later specifications.
-
A.
RFC 2797
RFC 2797 is an Internet standards document that originally specified the Certificate Management Messages over CMS (CMC) protocol for managing X.509 digital certificates.
-
B.
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.
-
C.
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.
-
D.
RFC 2796
RFC 2796 is an Internet Engineering Task Force (IETF) document that specified an early version of the Multiprotocol Extensions for BGP-4 used to support multiple network layer protocols in inter-domain routing.
-
E.
RFC 2792
RFC 2792 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
- 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_6a0b0c554fac81908e6159bba70e310e |
completed | May 18, 2026, 12:55 p.m. |
| NEDg | Description generation | batch_6a0b0cfa58cc819085e976bf76fbf149 |
completed | May 18, 2026, 12:58 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0b0d534f1481908e74f754426d321f |
completed | May 18, 2026, 1 p.m. |
Created at: April 16, 2026, 6:53 p.m.