Triple

T2716760
Position Surface form Disambiguated ID Type / Status
Subject HelloSign E59982 entity
Predicate offers P178 FINISHED
Object HelloSign for Salesforce E59982 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: HelloSign for Salesforce | Statement: [HelloSign, offers, HelloSign for Salesforce]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HelloSign for Salesforce
Context triple: [HelloSign, offers, HelloSign for Salesforce]
  • A. HelloSign chosen
    HelloSign is an electronic signature and digital document workflow platform that enables users to sign, send, and manage legally binding documents online.
  • B. DocuSign
    DocuSign is a leading electronic signature and digital transaction management company that enables users to securely sign, send, and manage documents online.
  • C. Adobe Document Cloud
    Adobe Document Cloud is Adobe’s integrated suite of cloud-based services and apps for creating, editing, managing, and securely sharing PDF documents across devices.
  • D. DocSend
    DocSend is a document-sharing and tracking platform designed for securely sending files and gaining analytics on how recipients engage with them.
  • E. docuverse
    Docuverse is Ted Nelson’s visionary concept of a universal, interconnected digital library where all documents are permanently linked and traceable across a global hypertext system.
  • 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_69ab4ac92a088190bc74bca14038e3de completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abda964d4881908179b2a1b16411e4 completed March 7, 2026, 7:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69afb68c3ccc81909995d17651af27ed completed March 10, 2026, 6:13 a.m.
Created at: March 6, 2026, 9:55 p.m.