Triple
T21802405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2790
RFC 2790 is an Internet standards document that originally specified a Management Information Base (MIB) for managing IP version 4 routing tables via SNMP.
|
E1532095
|
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 2790 | Statement: [RFC 4632, obsoletes, RFC 2790]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2790 Context triple: [RFC 4632, obsoletes, RFC 2790]
-
A.
RFC 2770
RFC 2770 is an Internet Engineering Task Force (IETF) document that originally specified experimental IPv4 address allocation practices before being superseded by later standards.
-
B.
RFC 2779
RFC 2779 is an older Internet standard that defined requirements for presence and instant messaging systems before being superseded by later specifications.
-
C.
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.
-
D.
RFC 2792
RFC 2792 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
-
E.
RFC 2197
RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
- 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 2790 Triple: [RFC 4632, obsoletes, RFC 2790]
Generated description
RFC 2790 is an Internet standards document that originally specified a Management Information Base (MIB) for managing IP version 4 routing tables via SNMP.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2790 Target entity description: RFC 2790 is an Internet standards document that originally specified a Management Information Base (MIB) for managing IP version 4 routing tables via SNMP.
-
A.
RFC 2770
RFC 2770 is an Internet Engineering Task Force (IETF) document that originally specified experimental IPv4 address allocation practices before being superseded by later standards.
-
B.
RFC 2779
RFC 2779 is an older Internet standard that defined requirements for presence and instant messaging systems before being superseded by later specifications.
-
C.
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.
-
D.
RFC 2792
RFC 2792 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
-
E.
RFC 2197
RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
- 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_6a0ae042c3088190a5307a5f6e6be184 |
completed | May 18, 2026, 9:47 a.m. |
| NEDg | Description generation | batch_6a0ae18a2e608190a363697e587b26ed |
completed | May 18, 2026, 9:53 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0ae1e16fac8190b0b56d00a87d173f |
completed | May 18, 2026, 9:54 a.m. |
Created at: April 16, 2026, 6:53 p.m.