Triple

T21802370
Position Surface form Disambiguated ID Type / Status
Subject RFC 4632 E538268 entity
Predicate obsoletes P101 FINISHED
Object RFC 1817 NE NERFINISHED

How this triple was built (3 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 1817 | Statement: [RFC 4632, obsoletes, RFC 1817]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 1817
Context triple: [RFC 4632, obsoletes, RFC 1817]
  • A. RFC 1870
    RFC 1870 is an earlier Internet standards document that defined support for extended SMTP message sizes before being superseded by RFC 2821.
  • B. RFC 1847
    RFC 1847 is an early Internet standards document that defined a general framework for security multiparts in MIME email, laying groundwork for later secure messaging specifications.
  • C. RFC 1771
    RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
  • D. RFC 1657
    RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
  • E. RFC 1813
    RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 1817
Target entity description: RFC 1817 was an early Internet standards document that specified guidelines for Classless Inter-Domain Routing (CIDR) and IP address allocation before being superseded by later updates.
  • A. RFC 1870
    RFC 1870 is an earlier Internet standards document that defined support for extended SMTP message sizes before being superseded by RFC 2821.
  • B. RFC 1847
    RFC 1847 is an early Internet standards document that defined a general framework for security multiparts in MIME email, laying groundwork for later secure messaging specifications.
  • C. RFC 1771
    RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
  • D. RFC 1657
    RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
  • E. RFC 1813
    RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
  • F. None of above. chosen

Provenance (2 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_69e0c4733f4081909a86622e7e6d15d2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0780062688190a6c3a2a0364f0f77 completed April 28, 2026, 9:04 a.m.
Created at: April 16, 2026, 6:53 p.m.