Triple

T286792
Position Surface form Disambiguated ID Type / Status
Subject TFTP E5902 entity
Predicate originalRfc P10378 FINISHED
Object RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
E45563 NE FINISHED

How this triple was built (5 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 783 | Statement: [TFTP, originalRfc, RFC 783]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 783
Context triple: [TFTP, originalRfc, RFC 783]
  • A. 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.
  • B. RFC 883
    RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
  • C. RFC 855
    RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
  • D. RFC 1350
    RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
  • 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 783
Triple: [TFTP, originalRfc, RFC 783]
Generated description
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 783
Target entity description: RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
  • A. 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.
  • B. RFC 883
    RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
  • C. RFC 855
    RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
  • D. RFC 1350
    RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
  • 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
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originalRfc
Context triple: [TFTP, originalRfc, RFC 783]
  • A. originalText
    Indicates that one text is the initial, unmodified version from which other versions, translations, or representations are derived.
  • B. originalForm
    Indicates that one entity is the earlier, source, or initial version from which another entity is derived or transformed.
  • C. originalType
    Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
  • D. originalTextStatus
    Indicates the relationship between a text and its current state or condition relative to its original, unmodified form.
  • E. originalTextLanguage
    Indicates the language in which a text was originally written or created before any translation or adaptation.
  • F. None of above. chosen

Provenance (7 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_69a25946a7ac8190a78871c210213272 completed Feb. 28, 2026, 2:56 a.m.
NER Named-entity recognition batch_69a2605b372c8190831570aa6532cc96 completed Feb. 28, 2026, 3:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3e56fd6b88190b18e081386436ea9 completed March 1, 2026, 7:06 a.m.
NEDg Description generation batch_69a3e61ad63c8190940eaba657cd3df2 completed March 1, 2026, 7:09 a.m.
NED2 Entity disambiguation (via description) batch_69a3e668e05c8190ba92c581622756df completed March 1, 2026, 7:10 a.m.
PD Predicate disambiguation batch_69a25b7a8d148190aacdcc8ccb35c7f3 completed Feb. 28, 2026, 3:05 a.m.
PDg Predicate description generation batch_69a2605a3d988190a8872169fd8eb2e8 completed Feb. 28, 2026, 3:26 a.m.
Created at: Feb. 28, 2026, 3:02 a.m.