Triple

T8035965
Position Surface form Disambiguated ID Type / Status
Subject RFC 822 E187107 entity
Predicate standardizes P1371 FINISHED
Object ARPA Internet text message format E708916 NE FINISHED

How this triple was built (2 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: ARPA Internet text message format | Statement: [RFC 822, standardizes, ARPA Internet text message format]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ARPA Internet text message format
Context triple: [RFC 822, standardizes, ARPA Internet text message format]
  • A. Standard for the Format of ARPA Internet Text Messages chosen
    Standard for the Format of ARPA Internet Text Messages is the seminal specification that defined the syntax and structure of electronic mail messages on the early ARPANET, forming the basis for modern Internet email formats.
  • B. ARPANET Interface Message Processor platform
    The ARPANET Interface Message Processor platform was the specialized packet-switching computer system that formed the backbone of the early ARPANET, handling data routing between host machines in the first large-scale packet-switched network.
  • C. ARPANET protocol suite
    The ARPANET protocol suite was the early set of network communication protocols used on the ARPANET, serving as a precursor to and foundation for the modern Internet protocol suite (TCP/IP).
  • D. RFC 1022
    RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
  • 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.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca82ae2d1081909dbfee42b41db419 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3ef68c6081908727d17238b3522a completed March 31, 2026, 3:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc63cb39a48190b4d987295b5aa1b2 completed April 1, 2026, 12:16 a.m.
Created at: March 30, 2026, 5:22 p.m.