Triple

T5959130
Position Surface form Disambiguated ID Type / Status
Subject RFC 3711 E132589 entity
Predicate documentSeries P23871 FINISHED
Object RFC E5627 NE FINISHED

Named-entity recognition

Before disambiguation, gpt-5-mini classified whether the object phrase is a named entity — the step behind the object's NE type shown above.

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 | Statement: [RFC 3711, documentSeries, RFC]

Disambiguation candidates (1 decision)

The exact options the model was shown at each disambiguation step, with the option it chose highlighted — the evidence behind this triple's disambiguated ids.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC
Context triple: [RFC 3711, documentSeries, RFC]
  • A. RFC
    RFC is the commonly used abbreviation for Reading Football Club, a professional English football team based in Reading, Berkshire.
  • B. RFCs chosen
    RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
  • C. RFC 1
    RFC 1 is the first Request for Comments document, published in 1969, which laid the groundwork for the development of the ARPANET and the modern Internet protocol standards process.
  • D. RFC Editor
    The RFC Editor is the organization responsible for editing, publishing, and maintaining the Request for Comments (RFC) series that documents standards and technical notes for the Internet community.
  • E. RFC Series Working Group
    The RFC Series Working Group is an IETF body responsible for defining policies and processes that govern the publication and evolution of the Request for Comments (RFC) document series.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

Stage Batch ID Job type Status
creating batch_69c0086c2364819091e9fe2f58fa2517 elicitation completed
NER batch_69c039fbf49881909d97b4abb3c5286d ner completed
NED1 batch_69c0e3e3736c8190b445156f0c1bdf1f ned_source_triple completed
Created at: March 22, 2026, 4:02 p.m.