Triple
T36795174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmonized Sales Tax |
E909162
|
entity |
| Predicate | remittedBy |
P186304
|
FINISHED |
| Object | registered businesses |
—
|
LITERAL 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: registered businesses | Statement: [Harmonized Sales Tax, remittedBy, registered businesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remittedBy Context triple: [Harmonized Sales Tax, remittedBy, registered businesses]
-
A.
remittanceRole
Indicates the specific function or capacity an entity has in relation to sending, receiving, or processing a remittance.
-
B.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
C.
isRemittanceDependent
Indicates that one party’s financial situation or obligations rely significantly on receiving remittance payments from another party.
-
D.
transferredWith
Indicates that something was moved or conveyed from one entity to another using a specified medium, method, or accompanying item.
-
E.
foreignRecipient
Indicates that something is received by an entity located in or belonging to a different country or jurisdiction than the source.
- F. None of above. chosen
Provenance (4 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabdd2d88190be1c8de7e499cb83 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7ca91f1808190b2a05c4b691da0bb |
completed | May 3, 2026, 10:22 p.m. |
Created at: May 3, 2026, 4:12 p.m.