Triple

T10174617
Position Surface form Disambiguated ID Type / Status
Subject RFC 974 E235818 entity
Predicate obsoletedBy P101 FINISHED
Object RFC 2821 E210669 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 2821 | Statement: [RFC 974, obsoletedBy, RFC 2821]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 2821
Context triple: [RFC 974, obsoletedBy, RFC 2821]
  • A. RFC 2821 chosen
    RFC 2821 is an earlier Internet standard that defined the Simple Mail Transfer Protocol (SMTP) for email transmission before being superseded by RFC 5321.
  • B. RFC 5321
    RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
  • C. 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.
  • 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 821
    RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
  • 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_69ca84d1d5f88190ab878a1021ecff68 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdecd26a8c8190a391b9d5e47ebb72 completed April 2, 2026, 4:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69d3011742b48190bc8b8b6ba03c32b0 completed April 6, 2026, 12:40 a.m.
Created at: March 30, 2026, 9:11 p.m.