Triple

T21191718
Position Surface form Disambiguated ID Type / Status
Subject RFC 6081 E522225 entity
Predicate hasAbbreviation P43 FINISHED
Object RFC6081 NE NERFINISHED

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: RFC6081 | Statement: [RFC 6081, hasAbbreviation, RFC6081]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC6081
Context triple: [RFC 6081, hasAbbreviation, RFC6081]
  • A. RFC 6081 chosen
    RFC 6081 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve IPv6 connectivity across IPv4 networks with NAT.
  • B. RFC 5661
    RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
  • C. RFC 6186
    RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
  • D. RFC 5061
    RFC 5061 is an Internet Engineering Task Force (IETF) specification that extends and enhances the Stream Control Transmission Protocol (SCTP), particularly for dynamic address reconfiguration and improved transport flexibility.
  • E. RFC 5891
    RFC 5891 is an Internet standard that defines the protocol requirements and processing rules for Internationalized Domain Names (IDNs) in applications as part of the IDNA2008 framework.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e733381f288190b3da795f62a39568 completed April 21, 2026, 8:20 a.m.
Created at: April 16, 2026, 3:07 p.m.