Triple
T13551722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1812 |
E323663
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1716
RFC 1716 is an early Internet standards document that provided guidelines and requirements for IP routers before being superseded by RFC 1812.
|
E1047317
|
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 1716 | Statement: [RFC 1812, obsoletes, RFC 1716]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1716 Context triple: [RFC 1812, obsoletes, RFC 1716]
-
A.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
B.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
C.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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 1716 Triple: [RFC 1812, obsoletes, RFC 1716]
Generated description
RFC 1716 is an early Internet standards document that provided guidelines and requirements for IP routers before being superseded by RFC 1812.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1716 Target entity description: RFC 1716 is an early Internet standards document that provided guidelines and requirements for IP routers before being superseded by RFC 1812.
-
A.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
B.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
C.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaff0a6548190b8cde5084cef0061 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75da721208190a3f5159125dbde9a |
completed | May 3, 2026, 2:37 p.m. |
| NEDg | Description generation | batch_69f75ec5101081909652b0c0998b36c8 |
completed | May 3, 2026, 2:42 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f75f4a3b0c81908c0ca0351771953b |
completed | May 3, 2026, 2:44 p.m. |
Created at: April 9, 2026, 9:46 p.m.