Triple

T18564636
Position Surface form Disambiguated ID Type / Status
Subject RFC 3986 E453731 entity
Predicate obsoletes P101 FINISHED
Object RFC 2396 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 2396 | Statement: [RFC 3986, obsoletes, RFC 2396]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 2396
Context triple: [RFC 3986, obsoletes, RFC 2396]
  • A. RFC 3986
    RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
  • B. RFC 2068
    RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
  • C. RFC 1939
    RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
  • D. RFC 923
    RFC 923 is an Internet standards document that superseded RFC 870 by updating and refining specifications related to early Internet protocol operations.
  • E. RFC 2197
    RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
  • 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 2396
Target entity description: RFC 2396 is an earlier Internet standard that defined the generic syntax of Uniform Resource Identifiers (URIs) before being superseded by RFC 3986.
  • A. RFC 3986
    RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
  • B. RFC 2068
    RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
  • C. RFC 1939
    RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
  • D. RFC 923
    RFC 923 is an Internet standards document that superseded RFC 870 by updating and refining specifications related to early Internet protocol operations.
  • E. RFC 2197
    RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
  • 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.