Triple
T10216658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1657 |
E242461
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 4273
RFC 4273 is an Internet Engineering Task Force (IETF) standards document that defines the Management Information Base (MIB) for the Border Gateway Protocol version 4 (BGP-4), updating and replacing earlier BGP MIB specifications.
|
E850695
|
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 4273 | Statement: [RFC 1657, obsoletedBy, RFC 4273]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4273 Context triple: [RFC 1657, obsoletedBy, RFC 4273]
-
A.
RFC 4787
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
B.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
C.
RFC 2573
RFC 2573 is an IETF standard that specifies the SNMPv3 applications, including command generator and responder, notification originator and receiver, and proxy forwarder functionality for network management.
-
D.
RFC 4172
RFC 4172 is an IETF standards document that specifies the Internet Fibre Channel Protocol (iFCP), enabling the transport of Fibre Channel frames over IP networks.
-
E.
RFC 4303
RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
- 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 4273 Triple: [RFC 1657, obsoletedBy, RFC 4273]
Generated description
RFC 4273 is an Internet Engineering Task Force (IETF) standards document that defines the Management Information Base (MIB) for the Border Gateway Protocol version 4 (BGP-4), updating and replacing earlier BGP MIB specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4273 Target entity description: RFC 4273 is an Internet Engineering Task Force (IETF) standards document that defines the Management Information Base (MIB) for the Border Gateway Protocol version 4 (BGP-4), updating and replacing earlier BGP MIB specifications.
-
A.
RFC 4787
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
B.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
C.
RFC 2573
RFC 2573 is an IETF standard that specifies the SNMPv3 applications, including command generator and responder, notification originator and receiver, and proxy forwarder functionality for network management.
-
D.
RFC 4172
RFC 4172 is an IETF standards document that specifies the Internet Fibre Channel Protocol (iFCP), enabling the transport of Fibre Channel frames over IP networks.
-
E.
RFC 4303
RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa6e544c8190961cdd7f1fbe24e6 |
completed | April 6, 2026, 12:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6a804e8748190b4ebcfa9a0bb889f |
completed | April 8, 2026, 7:09 p.m. |
| NEDg | Description generation | batch_69d6d0003434819093e3f82a556db79c |
completed | April 8, 2026, 10 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d6df3c8f748190923db41ef1a9a03a |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 6, 2026, 11:06 a.m.