Triple

T10050114
Position Surface form Disambiguated ID Type / Status
Subject RFC 5322 E207723 entity
Predicate obsoletes P101 FINISHED
Object RFC 2822 E708917 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: RFC 2822 | Statement: [RFC 5322, obsoletes, RFC 2822]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 2822
Context triple: [RFC 5322, obsoletes, RFC 2822]
  • A. RFC 2822 chosen
    RFC 2822 is an Internet standard that defines the format for text-based email messages, updating and replacing the earlier RFC 822 specification.
  • B. RFC 822
    RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
  • C. RFC 5322
    RFC 5322 is the Internet standard that defines the syntax and format of text-based email messages, including headers such as From, To, Subject, and Date.
  • D. RFC 3821
    RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
  • E. RFC 3821
    RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over IP networks.
  • 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_69ca835ad0608190b7c80b292da004f5 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cdcf8e41c4819091fa12742197e207 completed April 2, 2026, 2:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2829674f08190b5f9c3b984106469 completed April 5, 2026, 3:41 p.m.
Created at: March 30, 2026, 8:56 p.m.