Triple

T1054621
Position Surface form Disambiguated ID Type / Status
Subject Jon Postel E22773 entity
Predicate notableWork P4 FINISHED
Object RFC 768
RFC 768 is the Internet standard that defines the User Datagram Protocol (UDP), a core transport-layer protocol used for low-latency, connectionless data transmission.
E121262 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 768 | Statement: [Jon Postel, notableWork, RFC 768]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 768
Context triple: [Jon Postel, notableWork, RFC 768]
  • A. RFC 791
    RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
  • B. RFC 793
    RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
  • C. RFC 826
    RFC 826 is the Internet standard document that specifies the Address Resolution Protocol (ARP), which maps IP addresses to physical hardware addresses on local networks.
  • D. RFC 792
    RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
  • E. RFC 882
    RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
  • 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 768
Triple: [Jon Postel, notableWork, RFC 768]
Generated description
RFC 768 is the Internet standard that defines the User Datagram Protocol (UDP), a core transport-layer protocol used for low-latency, connectionless data transmission.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 768
Target entity description: RFC 768 is the Internet standard that defines the User Datagram Protocol (UDP), a core transport-layer protocol used for low-latency, connectionless data transmission.
  • A. RFC 791
    RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
  • B. RFC 793
    RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
  • C. RFC 826
    RFC 826 is the Internet standard document that specifies the Address Resolution Protocol (ARP), which maps IP addresses to physical hardware addresses on local networks.
  • D. RFC 792
    RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
  • E. RFC 882
    RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
  • 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_69a493da02e081908c13ff5e02a0fe7a completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b8d79268819080f3f3f497e91c58 completed March 1, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac3bd110ac8190b66163de42bd3034 completed March 7, 2026, 2:53 p.m.
NEDg Description generation batch_69ac3d4b32348190883244f2b8af32a0 completed March 7, 2026, 2:59 p.m.
NED2 Entity disambiguation (via description) batch_69ac3dbf5c70819084a942fc97a9b50f completed March 7, 2026, 3:01 p.m.
Created at: March 1, 2026, 7:42 p.m.