Triple

T14547498
Position Surface form Disambiguated ID Type / Status
Subject RFC 3650 E341325 entity
Predicate hasCompanionDocument P114884 FINISHED
Object RFC 3651 E344687 NE FINISHED

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 3651 | Statement: [RFC 3650, hasCompanionDocument, RFC 3651]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 3651
Context triple: [RFC 3650, hasCompanionDocument, RFC 3651]
  • A. RFC 3651 chosen
    RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
  • B. RFC 3851
    RFC 3851 is the original specification for S/MIME Version 3.1, defining how to provide cryptographic security services for MIME data such as email.
  • C. RFC 3610
    RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
  • D. RFC 3652
    RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
  • E. RFC 3655
    RFC 3655 is an Internet Engineering Task Force (IETF) document that was an earlier specification later superseded by the DNS Security (DNSSEC)–related standard defined in RFC 4033.
  • 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: hasCompanionDocument
Context triple: [RFC 3650, hasCompanionDocument, RFC 3651]
  • A. hasCompanionCandidate
    Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
  • B. hasCompanionOrganization
    Indicates that one organization is associated with another organization that accompanies, supports, or partners it in some related capacity.
  • C. hasNotableDocument
    Indicates that an entity is associated with a document that is considered significant, noteworthy, or of particular importance.
  • D. hasOfficialDocument
    Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
  • E. hasCompanionPillar
    Indicates that an entity is associated with or supported by a corresponding companion pillar.
  • F. None of above. chosen

Provenance (5 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2ebdf9481909f4d2da1ad31099c completed April 14, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd7a6344b08190a3c1124c6dd7da96 completed May 8, 2026, 5:53 a.m.
PD Predicate disambiguation batch_69de5c546c7081909e27d504ec360c5c completed April 14, 2026, 3:25 p.m.
PDg Predicate description generation batch_69de610330a48190b558235a14c0dc9f completed April 14, 2026, 3:45 p.m.
Created at: April 10, 2026, 1:23 a.m.