Triple
T12282168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HelloFax, Inc. |
E292740
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | HelloSign |
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 | Statement: [HelloFax, Inc., successor, HelloSign]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HelloSign Context triple: [HelloFax, Inc., successor, HelloSign]
-
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.
Zoho Sign
Zoho Sign is a cloud-based electronic signature and digital document management service that enables users to securely sign, send, and manage legally binding documents online.
-
D.
Zoho Docs
Zoho Docs is a cloud-based document management and collaboration platform that allows users to create, store, share, and manage files online as part of the Zoho productivity suite.
-
E.
DocSend
DocSend is a document-sharing and tracking platform designed for securely sending files and gaining analytics on how recipients engage with them.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cf2b09c81908a11581d33f65be0 |
completed | April 10, 2026, 3:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62a97614c8190b67e07df3e424e32 |
completed | May 2, 2026, 4:47 p.m. |
Created at: April 8, 2026, 9:52 p.m.