Triple

T7928549
Position Surface form Disambiguated ID Type / Status
Subject RFC 4271 E184128 entity
Predicate obsoletes P101 FINISHED
Object 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.
 E708267 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 1771 | Statement: [RFC 4271, obsoletes, RFC 1771]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 1771
Context triple: [RFC 4271, obsoletes, RFC 1771]
  • A. 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.
  • 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 1670
    RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
  • E. RFC 1497
    RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
  • 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 1771
Triple: [RFC 4271, obsoletes, RFC 1771]
Generated description
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.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 1771
Target entity description: 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.
  • A. 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.
  • 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 1670
    RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
  • E. RFC 1497
    RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
  • 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_69ca828fe7bc819090f52c88dcd72183 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3ac9ac4c819082cd2190fc3ce5a2 completed March 31, 2026, 3:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc5643fd3081908fc9a413a7920145 completed March 31, 2026, 11:18 p.m.
NEDg Description generation batch_69cc58a76b90819092de63b3b23e70af completed March 31, 2026, 11:28 p.m.
NED2 Entity disambiguation (via description) batch_69cc5cfccc9c8190adcbaee96c17711e completed March 31, 2026, 11:47 p.m.
Created at: March 30, 2026, 5:07 p.m.