Triple
T12282167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HelloFax, Inc. |
E292740
|
entity |
| Predicate | product |
P490
|
FINISHED |
| Object | HelloFax |
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: HelloFax | Statement: [HelloFax, Inc., product, HelloFax]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HelloFax Context triple: [HelloFax, Inc., product, HelloFax]
-
A.
HelloFax, Inc.
HelloFax, Inc. was the original name of HelloSign, a company providing electronic signature and digital document workflow solutions.
-
B.
FAX
FAX is the public bus transit system serving the city of Fresno, California.
-
C.
Innovapost
Innovapost is an information technology and shared services company that provides IT solutions and support for Canada Post and its affiliated organizations.
-
D.
HelloSign
chosen
HelloSign is an electronic signature and digital document workflow platform that enables users to sign, send, and manage legally binding documents online.
-
E.
GoSend
GoSend is Gojek’s on-demand courier and delivery service that enables users to send packages quickly within a city.
- 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.