Triple

T10069115
Position Surface form Disambiguated ID Type / Status
Subject RFC 2060 E213172 entity
Predicate title P38 FINISHED
Object Internet Message Access Protocol - Version 4rev1 E39860 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: Internet Message Access Protocol - Version 4rev1 | Statement: [RFC 2060, title, Internet Message Access Protocol - Version 4rev1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Internet Message Access Protocol - Version 4rev1
Context triple: [RFC 2060, title, Internet Message Access Protocol - Version 4rev1]
  • A. Multipurpose Internet Mail Extensions
    Multipurpose Internet Mail Extensions (MIME) is an Internet standard that extends the format of email to support text in character sets beyond ASCII as well as attachments like images, audio, video, and application files.
  • B. RFC 3501 chosen
    RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
  • C. IMAP
    IMAP (Internet Message Access Protocol) is a standard email protocol that allows clients to access and manage messages stored on a mail server while keeping them synchronized across multiple devices.
  • D. SMTP Service Extension for Secure SMTP over Transport Layer Security
    SMTP Service Extension for Secure SMTP over Transport Layer Security is an IETF standard (RFC 3207) that defines how to use TLS to provide encryption and secure authentication for SMTP email transmissions.
  • E. 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.
  • 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_69ca83977128819084084eb7d1d8c52a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdcff8d9c08190bc030f1dcc696310 completed April 2, 2026, 2:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d29a96fc888190aec7cd364a0d7fb1 completed April 5, 2026, 5:23 p.m.
Created at: March 30, 2026, 8:58 p.m.