Triple

T1631437
Position Surface form Disambiguated ID Type / Status
Subject RFC 821 E35264 entity
Predicate messageFormatSpecifiedBy P130 FINISHED
Object RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
E187107 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 822 | Statement: [RFC 821, messageFormatSpecifiedBy, RFC 822]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 822
Context triple: [RFC 821, messageFormatSpecifiedBy, RFC 822]
  • A. RFC 821
    RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
  • B. 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.
  • C. RFC 5321
    RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
  • D. RFC 883
    RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
  • E. RFC 3501
    RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
  • 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 822
Triple: [RFC 821, messageFormatSpecifiedBy, RFC 822]
Generated description
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 822
Target entity description: RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
  • A. RFC 821
    RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
  • B. 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.
  • C. RFC 5321
    RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
  • D. RFC 883
    RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
  • E. RFC 3501
    RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
  • F. None of above. chosen
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: messageFormatSpecifiedBy
Context triple: [RFC 821, messageFormatSpecifiedBy, RFC 822]
  • A. format chosen
    Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
  • B. intendedMessage
    Indicates that one entity is the message or content that another entity aims or plans to communicate.
  • C. messageIntroducedWith
    Indicates that one message is presented or initiated by means of another message or introductory content.
  • D. notationPattern
    Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
  • E. singleMatchFormatIntroduced
    Indicates that a particular single-match competition format was introduced or first implemented.
  • F. None of above.

Provenance (6 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_69a886036bc081909ff5de16dbe5e8ea completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9431af5ac8190893133f1ae490142 completed March 5, 2026, 8:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad6815c4588190bccfbece8f22c1a1 completed March 8, 2026, 12:14 p.m.
NEDg Description generation batch_69ad686f4a0c819091f99800d6618ecb completed March 8, 2026, 12:15 p.m.
NED2 Entity disambiguation (via description) batch_69ad68f00e8c8190b2cbf3d921dce5a8 completed March 8, 2026, 12:17 p.m.
PD Predicate disambiguation batch_69a907c91c888190b6ed295c1a2e0977 completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:28 p.m.