Triple

T18564637
Position Surface form Disambiguated ID Type / Status
Subject RFC 3986 E453731 entity
Predicate obsoletes P101 FINISHED
Object RFC 2732 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 2732 | Statement: [RFC 3986, obsoletes, RFC 2732]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 2732
Context triple: [RFC 3986, obsoletes, RFC 2732]
  • A. RFC 3207
    RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
  • B. RFC 1442
    RFC 1442 is an early Internet standards document that defined the Structure of Management Information (SMI) for version 2 of the Simple Network Management Protocol (SNMPv2).
  • C. RFC 2447
    RFC 2447 is an Internet standards document that originally specified how to integrate iCalendar-based scheduling with email using the iMIP protocol.
  • D. RFC 3652
    RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
  • E. RFC 1652
    RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
  • 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 2732
Target entity description: RFC 2732 is an Internet standards document that specified the use of bracketed IPv6 addresses in URLs before being superseded by RFC 3986.
  • A. RFC 3207
    RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
  • B. RFC 1442
    RFC 1442 is an early Internet standards document that defined the Structure of Management Information (SMI) for version 2 of the Simple Network Management Protocol (SNMPv2).
  • C. RFC 2447
    RFC 2447 is an Internet standards document that originally specified how to integrate iCalendar-based scheduling with email using the iMIP protocol.
  • D. RFC 3652
    RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
  • E. RFC 1652
    RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
  • 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_69d8d38974308190a9174430ef256b73 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53afd8114819093b57d86f8213311 completed April 19, 2026, 8:28 p.m.
Created at: April 10, 2026, 11:42 a.m.