Triple

T10157785
Position Surface form Disambiguated ID Type / Status
Subject RFC 959 E233815 entity
Predicate obsoletes P101 FINISHED
Object RFC 765
RFC 765 was an early specification of the File Transfer Protocol (FTP) that defined how files are transferred over TCP/IP networks before being superseded by later standards.
 E845074 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 765 | Statement: [RFC 959, obsoletes, RFC 765]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 765
Context triple: [RFC 959, obsoletes, RFC 765]
  • A. RFC 760
    RFC 760 is an early Internet standard document authored by Jon Postel that specifies the original Internet Protocol (IP).
  • B. RFC 761
    RFC 761 is an early Internet standard document that specifies the Transmission Control Protocol (TCP), within which Postel’s law was famously articulated.
  • C. RFC 1665
    RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • D. RFC 2765
    RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
  • E. RFC 857
    RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
  • 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 765
Triple: [RFC 959, obsoletes, RFC 765]
Generated description
RFC 765 was an early specification of the File Transfer Protocol (FTP) that defined how files are transferred over TCP/IP networks before being superseded by later standards.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 765
Target entity description: RFC 765 was an early specification of the File Transfer Protocol (FTP) that defined how files are transferred over TCP/IP networks before being superseded by later standards.
  • A. RFC 760
    RFC 760 is an early Internet standard document authored by Jon Postel that specifies the original Internet Protocol (IP).
  • B. RFC 761
    RFC 761 is an early Internet standard document that specifies the Transmission Control Protocol (TCP), within which Postel’s law was famously articulated.
  • C. RFC 1665
    RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
  • D. RFC 2765
    RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
  • E. RFC 857
    RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
  • 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_69ca848e80748190b91d1e04d35512c7 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec5507f08190b47f797bacd5640c completed April 2, 2026, 4:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d300acae608190891d8f55c3d5102b completed April 6, 2026, 12:39 a.m.
NEDg Description generation batch_69d302537a548190b211727dd124cba6 completed April 6, 2026, 12:46 a.m.
NED2 Entity disambiguation (via description) batch_69d3033245448190bcc802b7dbd274fc completed April 6, 2026, 12:49 a.m.
Created at: March 30, 2026, 9:09 p.m.