Triple

T22375538
Position Surface form Disambiguated ID Type / Status
Subject vCard E553142 entity
Predicate updatedInRFC P83873 FINISHED
Object RFC 6350 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 6350 | Statement: [vCard, updatedInRFC, RFC 6350]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 6350
Context triple: [vCard, updatedInRFC, RFC 6350]
  • A. RFC 6350 chosen
    RFC 6350 is the IETF standard specification that defines the vCard format for representing and exchanging personal contact information in a structured, text-based form.
  • B. RFC 6410
    RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
  • C. RFC 7530
    RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
  • D. RFC 6352
    RFC 6352 is the Internet standards document that specifies the CardDAV protocol for remote access and management of contact data stored on a server.
  • E. RFC 6052
    RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: updatedInRFC
Context triple: [vCard, updatedInRFC, RFC 6350]
  • A. deprecatedInRFC
    Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
  • B. hasRFC chosen
    Indicates that an entity is associated with, described by, or defined in a specific RFC (Request for Comments) document.
  • C. originalRfc
    Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
  • D. updatedIn
    Indicates that an entity has undergone a change or modification within a specified time period or version context.
  • E. updated
    Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
  • F. None of above.

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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15807cb748190abd9adc08ca1ad4f completed April 29, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69e73011e6388190a05edf137f488441 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 8:45 p.m.